Generate primary key automatically

Hi, I'd like to know how to generate primary keys automatically with JHeadStart because when I try to make an insert into a table, the page gives me the option of insert the primary key of the register.
Thanks a lot

I have a table which have 2 fields, one of those is the primary key, the other is the description.
I have established the primary key as a DBSequence, but when I try to insert a new record testing the service, appears a negative number in the primary key and instead of that I want to appear the correspondent key, or if doesn't appear the correct value, the insert be done correctly.
At least I change manually the value if this key, the insert can't be done.

Similar Messages

How generate primary key atumatically in jdeveloper 10g

Hi,
I am using jdev 10g. I created a fusion web applicaton.
I am not getting any option to generate primary key from sequence automatically.
In Jdev11g we can create by trigger easily.
Please help
Thanks
Raj

Hi Raj,
Check this link
[http://download.oracle.com/docs/html/B25947_01/bcentities006.htm#sm0147|http://download.oracle.com/docs/html/B25947_01/bcentities006.htm#sm0147]
Regards,
Vikram

Sequences to generate primary keys

Hi,
A question on using sequences to generate primary keys. We have a table and in all environments, test, uat, prod, a sequence exists to generate the primary key for the table. This table is a reference table and is not updateable by the users.
When developing scripts to insert records into the table, the developers are currently not using the sequence but typing in unique numbers so data scripts consist of something like this:
INSERT INTO EMPLOYEE_GROUP
(employee_group_id, code, description,...)
VALUES
(45,'sdf','sdfsdfsf');
INSERT INTO EMPLOYEE_GROUP
(employee_group_id, code, description,...)
VALUES
(46,'sdf','sdfsdfsf',...);
a) Is this normal practice?
b) Sometimes they are using the sequence to generate the primary key in development but then hardcoding the number in the script so in development the sequence might be at 160, but in the other environments the sequences will still be at one. Is this also normal practice?
My usual method in developing scripts is to use <seqeunce>.nextval but it's somewhat incompatitble in the current environment.

You are using a surrogate, or synthetic primary key. For a primary key generated in this way, the value is inconsequential. All that matters is that it is unique and the tables with foreign keys into it, if any, also have that value set properly. But it doesn't matter if the value is 1, 100, 12344, 2222222222, etc. All you care about is the uniqueness.
If you create the data properly then child records and their parents should be correct in all systems you mention, it's just that the actual value of the key will differ and that's fine. You care about the relationship of the records, not the value of the synthetic keys.

Generate the primary key automatically while records are saved

Hi experts,
I need to generate the primary key of a custom table automatically when a new record is saved. Pleas help asap. Urgent.

Hi Rob and vikas,
   Thanks for your answers . Both of the solutions you mentioned were syntactically correct and activated but they are not populating the numbers.In case of Rob's soultion I guess I am not able to catch the return number. I am giving the code below. So Please look into it,
FORM gen_manu_siteid .
data : number type zsiteid value 155.
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
    NR_RANGE_NR                   = '02'
    OBJECT                        = 'zmanusite'
    QUANTITY                      = '1'
SUBOBJECT                     = ' '
TOYEAR                        = '0000'
IGNORE_BUFFER                 = ' '
IMPORTING
    NUMBER                        = number
QUANTITY                      =
RETURNCODE                    =
EXCEPTIONS
INTERVAL_NOT_FOUND            = 1
NUMBER_RANGE_NOT_INTERN       = 2
OBJECT_NOT_FOUND              = 3
QUANTITY_IS_0                 = 4
QUANTITY_IS_NOT_1             = 5
INTERVAL_OVERFLOW             = 6
BUFFER_OVERFLOW               = 7
OTHERS                        = 8
*IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
*ENDIF.
ztblqm_sqm-zsiteid = number .
ENDFORM.                    " gen_manu_siteid
When this did not work. i tried Vikas's soution and the code i used for this is
FORM gen_manu_siteid .
data : w_count like ztblqm_sqm-zsiteid,
       e_wa like ztblqm_sqm occurs 0 with header line.
select max( zsiteid ) from ztblqm_sqm into w_count .
w_count = w_count + 1.
e_wa-zsiteid = w_count.
modify ztblqm_sqm from e_wa.
ENDFORM.                    " gen_manu_siteid
Please look into this and give me a solution.
NB: I have tried them at the event 01 include.

How to obtain automatically generated primary key

Are there any ways to obtain the value of a primary key which is generated automatically by a server?
Thanks.

Are there any ways to obtain the value of a primary
key which is generated automatically by a server?Yes, if you are using JDBC 3.0 and a driver that supports it.
You do something like this (from the JDBC getting started guid at http://java.sun.com/j2se/1.4/docs/guide/jdbc/getstart/statement.html#1000569):
String sql = "INSERT INTO AUTHORS (LAST, FIRST, HOME) VALUES " +
                                                  "'PARKER', 'DOROTHY', 'USA', keyColumn";
int rows = stmt.executeUpdate(sql,
                                                                Statement.RETURN_GENERATED_KEYS);
ResultSet rs = stmt.getGeneratedKeys();
if (rs.next()) {
        ResultSetMetaData rsmd = rs.getMetaData();
        int colCount = rsmd.getColumnCount();
        do {
                for (int i = 1; i <= colCount; i++) {
                        String key = rs.getString(i);
                        System.out.println("key " + i + "is " + key);
        while (rs.next();)
else {
        System.out.println("There are no generated keys.");
}

How to "auto" generate "Primary Key" in custom table?

Hi Folks,
Requirement:
I need a function module or program that can create automatically a primary key.
Scenario:
I have a program that creates an entries and save it to a custom table at the same time, but a primary key should always be generated respective to the entries saved.
Example:
Material(MATNR) 4001001, Plant(WERKS) XX01, ID[Primary Key-auto generated]
(I'm thinking of a similar concept/logic on how a unique IDOC number is being generated or how SAP standard creates a unique entry)
I try to look for any SAP FM that can generate a PK, but there's no luck.
Thanks.
Regards,
Jun

Hi Keshu and All,
The links are helpful, however:
#1. I don't have authorization to create a new object in transaction SNRO, but the way I see the objects in SNRO is just for defining the length(number of characters) for the ranges that will be use if I'm not mistaken.
#2. FM NUMBER_GET_NEXT - yes it can populate incremental unique entries but it's only occurring at runtime ?? So when the program get terminated it's not being saved nowhere.
So after if I use FM NUMBER_GET_NEXT, I always have to look for all the last primary key in my custom table, then target it as my starting point for creating a new PK. I think this will give a performance issue, any comments?
For better visualization, I have scenario:
1. (ZQ_CREATE_PK) Create unique incremental PK for material, batch, so on..
2. Append line/entries to ZQ_TABLE
3. Repeat #1 and #2
4. User exits the program
5. Back to 1 --> At this point, I need to get the "LATEST" PK then start this as a starting point again to generate PK and append it to ZQ_TABLE
I'm assuming that SAP has other SAP FMs related in creating this scenario. Similar to IDOC # creation..
Thanks.

Help required to generate primary key sequence

Hello All,
I need your help in generating a sequence for primary key in my db table created using java dictionary project in my NWDS 7.3.
The table column EMPL_ID is a primary and needs to be a sequence. The code in the JPA entity is as below. The underlying database is DB2 on Linux. Kindly help me resolve this issue.
* The persistent class for the TMP_EMPL_DATA database table.
@Entity
@Table(name="TMP_EMPL_DATA")
public class TmpEmplData implements Serializable {
     private static final long serialVersionUID = 1L;
     @Id
     @SequenceGenerator(name="EMPLID_GENERATOR", sequenceName="EMPID_SEQ", initialValue = 10000, allocationSize = 1)
     @GeneratedValue(strategy=GenerationType.SEQUENCE, generator="EMPLID_GENERATOR")
     @Column(name="EMPL_ID")
     private String _emplId_;
My bean class contains a public method as follows.
public TmpEmplData createEmployee(String employeeName, int age, String location)
         TmpEmplData emplData = new TmpEmplData();
         emplData.set_emplName_(employeeName);
         emplData.setAge(age);
         emplData.setLocation(location);
         entityManager.persist(emplData);
         entityManager.find(TmpEmplData.class, emplData.get_emplId_());
         return emplData;
During execution, i am getting an error as below.
Caused by: javax.persistence.PersistenceException: The generated SQL statement is not valid for the underlying database platform (platform no. 99). For more details see attached exception. SQL statement is SELECT NEXT VALUE FOR "EMPID_SEQ" FROM ( VALUES (1) )
at com.sap.engine.services.orpersistence.sqlmapper.mapping.JPASQLMapperImpl.createSequenceIDGeneratorSelectText(JPASQLMapperImpl.java:1239)
at com.sap.engine.services.orpersistence.entitymanager.CachedJPASQLMapper.createSequenceIDGeneratorSelectText(CachedJPASQLMapper.java:259)
at com.sap.engine.services.orpersistence.generator.GeneratorFactory.<init>(GeneratorFactory.java:156)
at com.sap.engine.services.orpersistence.entitymanager.EntityManagerFactoryImpl$MetaDataImpl.<init>(EntityManagerFactoryImpl.java:323)
at com.sap.engine.services.orpersistence.entitymanager.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:137)
at com.sap.engine.services.orpersistence.entitymanager.JtaEntityManagerFactoryImpl.<init>(JtaEntityManagerFactoryImpl.java:39)
at com.sap.engine.services.orpersistence.provider.PersistenceProviderImpl.createJtaEntityManagerFactory(PersistenceProviderImpl.java:251)
at com.sap.engine.services.orpersistence.provider.PersistenceProviderImpl.createContainerEntityManagerFactory(PersistenceProviderImpl.java:236)
at com.sap.engine.services.orpersistence.container.EMFInstanceCreator.getEntityManagerFactory(EMFInstanceCreator.java:134)
at com.sap.engine.services.orpersistence.container.ORPersistenceObjectFactory.getEMF(ORPersistenceObjectFactory.java:300)
at com.sap.engine.services.orpersistence.container.ORPersistenceObjectFactory.getObjectInstance(ORPersistenceObjectFactory.java:73)
at com.sap.engine.lib.injection.ReferenceObjectFactory.getObject(ReferenceObjectFactory.java:96)
at com.sap.engine.lib.injection.FieldInjector.inject(FieldInjector.java:113)
... 122 more
Caused by: com.sap.engine.services.orpersistence.sqlmapper.generate.SQLMappingException: SQL statement is not valid for underlying database platform.
at com.sap.engine.services.orpersistence.sqlmapper.common.CommonSQLMappingResult.getStatementString(CommonSQLMappingResult.java:237)
at com.sap.engine.services.orpersistence.sqlmapper.mapping.JPASQLMapperImpl.createSequenceIDGeneratorSelectText(JPASQLMapperImpl.java:1237)
... 134 more
Caused by: com.sap.sql.tree.StringRepresentationFailureException: Cannot represent next value expression as string.
at com.sap.sql.tree.impl.OpenSqlTextExpert.nextValueExpressionToText(OpenSqlTextExpert.java:185)
at com.sap.sql.tree.impl.NextValueExpressionBuilderImpl$NextValueExpressionImpl.toSqlTxt(NextValueExpressionBuilderImpl.java:140)
at com.sap.sql.tree.impl.AbstractSqlTextExpert.selectSublistToText(AbstractSqlTextExpert.java:130)
at com.sap.sql.tree.impl.SelectSublistImpl.toSqlTxt(SelectSublistImpl.java:150)
at com.sap.sql.tree.impl.QuerySpecificationImpl.toSqlTxt(QuerySpecificationImpl.java:361)
at com.sap.sql.tree.impl.SelectStatementImpl.toSqlTxt(SelectStatementImpl.java:139)
at com.sap.sql.tree.impl.SQLStatementImpl.toSqlString(SQLStatementImpl.java:75)
at com.sap.engine.services.orpersistence.sqlmapper.common.CommonSQLMappingResult.getStatementString(CommonSQLMappingResult.java:233)
... 135 more

Hi,
does the sequence exist? SAP JPA does not support creation of sequences, you have to create it manually.
Maybe SAP JPA also does not support DB2 sequences with "Open SQL" correctly.
- Tryp to set your data source to "native" or "vendor".
- Try to turn on oracle compatibility:
db2set DB2_COMPATIBILITY_VECTOR=ORA
Regards
Rolf

Is this good approach for generating Primary Keys ?

Hi,
All our EJBs are state less Session Beans.
We have created a state less Session(name SequenceEJB) for getting Primary Key.
Thre is a method,
int getSequenceNumber(String tableName,String fieldName) in SequenceEJB. And the following query is used in the above said method.
SELECT MAX("+fieldName+") ID FROM "+tableName
Each EJB will lookup SequenceEJB, and call the above said method for getting sequence number.
Is this approach sclable ?
Can we proceed by this approach ?
Thanks in advance
Srinivas

As long as you are in EJB, synchronization won't help you because it is not permitted by the EJB spec.
If you can go with JDBC 3.0 / Java 1.4, the statement interface supportes generated keys. See http://java.sun.com/j2se/1.4/docs/api/java/sql/Statement.html.
If you cannot go with JDBC 3.0 / Java 1.4, you can implement the key-generation db-specific (e.g. using oracle sequences for oracle tables, and whatever exists for DB2, SQL Server etc.) That of course requires special support for all databases, but at least you can run your app with different databases.
Or you can try to do it the following way, using a separate table for the keys.
ResultSet rs = statement.executeQuery("select id from mySequences");
oldId = rs.getInt(1);
newId = oldId + 1
int updatedRows = statement.executeQuery("update mySequences set id = newId where id = oldId");
if(updatedRows == 1) {
// succesful
} else {
// not sucessful, somebody else has already retrieve this id; do something like Thread.sleep() and retry
}This way, the database does the actual synchronization between the processes (each process sees the same data in the tables), and you implement the retry logic.

Master-detail with auto-generated primary key(master)

Hello,
I have the following master-detail setup:
Master - block A primary key is: codeA
Detail - block B
codeA is genrated only at commit time and is obtained from a sequence.
User needs to add detail records. This is easy to do since he has to click on the insert icon on the toolbar. At commit time, use commit_form.
Prob: the requirements as asked by the client is to add a button (which we will label INSERT DETAIL). When the user click on the button, it opens a window where he can enter the detail info then click on save. This should bring him back to the master-detail form and the record in the detail block is inserted.
What is the problem here ? since the detail block has the foreign key tied to the master primary key, the window-form (with the call_form) that we opened for the detail entry won't be able to save since at this point we still have not assigned a value for the primary key (and hence a value for the foreign key).
Possible Suggestions:
-Use a temp database table to hold the detail record from the second form and use it to transfer values to the detail record in the master-detail
-Use a global record group
-We can't use parameter list to pass back these values.
So my question is:
What would be the most efficient way to have an insert button on the detail block that would allow the user to have a pop up where he can insert his values and then be brought back to the master-detail.
Thanks.

Hello again,
May be I was not clear enough.
Scenario 1: We use the master-detail form as is with the default oolbar. In this case, the user can insert the detail records one by one without needing the primary-foreign key value since this is handled by default.
Once we save the form (commit_form), I use the pre-insert trigger to get the master block primary key generated from the sequence and since the detail block key is copied from this value, both are saved correctly and it is the end of the story.
Scenario 2: As explained in the initial post, the user will populate the detail records one by one by clicking on the -INSERT DETAIL- button and hence has a window where he can insert the detail info and then be brought back to the master-detail form every time he enters a new detail record.
The problem here is that I can't generate the primary key for the master block since the client has the following requirement:
The user can always change his mind and not complete, meaning save the form, his process
As such, the key should be generated in the last step before Commit.

JDO Auto Generate Primary Key

Hi
I am working with JDO.
I want to auto generate the primary key value that should increment for each entry into database.
How can i do it, please guide me.
Any link or doc will be appreciated.
Regards
Osman

There is only one answer to "how I do this" questions: read the manual.
Any link or doc will be appreciated.Google. Seriously dude, a forum is not your personal information service - go make some effort yourself. Come back when you have an actual problem that you need help with.

What to use in jpa from self generated primary key ?

Is it described somewhere what strategy to use with JPA when primary key are self generated by a trigger into the table ?
Thank You

Please see this link http://en.wikibooks.org/wiki/Java_Persistence/Identity_and_Sequencing#Primary_Keys_through_Triggers

How to use Oracle DB Sequence to Generate Primary Key Values?

Dear Members,
I am using Oracle JDev V 11.1.2.1.0 and Oracle 11g XE Database.
I have followed the below steps:-
1/ Created an EmployeesEO
2/ Created an EmployeesVO
3/ Created a JSPX Page
4/ On the JSPX Page I have dragged the EmployeesVO and created it in ADF Table Format.
On this page when I create a new record, I want to generate employee id automatically based on a sequence which is created in the database of the HR Schema.
Please let me know how to achieve the above requirement.
Many thanks in advance.
Regards.

check [url http://mjabr.wordpress.com/2011/03/11/make-sequence-number-as-default-value/]Set an attribute’s default value with a sequence number

Automatic Creation of primary key at the time of creating entries

Hi All,
I have a requirement to generate the primary key automatically at the time of creating entries. I have managed to do so by writing an event code for the maintainance object in SE54.
However called only when I create entries throught the Maintainance View.
It does not get called when I write an insert statement in the program.
Please suggest a way to achieve this.
Thanks in advance,
Archana.

for assigning the primary key while using insert statement, write a piece of code to get the last pk value, increment it by 1 and then assign this value to the pk field of the next record while inserting. if you are using a fn mod to insert values, just have this piece of code right before the insert query. a better way would be to use a GUID which will be unique globally. there is a fn mod GUID_CREATE which you can use to generate GUID. i don't think there is a way to automate this while making entries using se11, unless you change the code that actually creates the entry in the database.

Any easy way to generate unique primary key for database table?

I'm currently playing with the J2EE reference implementation from Sun which comes with the IBM Cloudscape database. This Cloudscape database supports the use of an AutoIncrement field.
First question: Can I use CMP and assume that the database will generate a proper key for me? Anyone tried it out successfully before?
Also, based on what I've heard so far, it seems that generating database primary key is not really well-supported by J2EE using CMP in that a lot of J2EE developers have to resort to workarounds like using a session bean, JDBC and (1) some seed numbers for ID implanted in the database itself (as in the J2EE tutorial DukesBankApp example) or (2) using the SQL MAX aggregation command + 1. Usign seed number is contradictory to good database design and using MAX is dangerous for heavy traffic application if 2 beans try to insert themselves into the database at the same time (synchronizarion problem).
Anyway I find it dumb that we still have to go back to JDBC and SQL which was the reason why the concept Entity Bean was introduced; to make database persistence transparent! Now it seems that J2EE makes it worse and more troublesome than before.
Second Question: Is there any easy (hopefully transparent/automatic) way of generating primary key ID?

if you want to rely on your container or database then go hard, will probably be faster.
to make a cross container/db soln I used a CMP Entity bean called Sequence with one field for uid
I use one instance and increment the field each time.
To do the logic, I have a utils class with static method, no need for session bean overhead
I reckon this approach is OK considering all things

Automatic primary key generation for pointbase

Hello friends,
I was wondering whether it is possible to automatically generate primary keys for a pointbase database. Just like the SQL Server pointbase also has a indentity property. I have used weblogic builder to specify automatic key generation. Through the pointbase console I can see that all the columns for all the tables are marked as nullable except the primary key columns. However when I try to insert data into the database using ejb. I get the exception :
javax.ejb.EJBException: EJB Exception:: java.sql.SQLException: Data exception -- null value not allowed. .
     at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown Source)
     at com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
     at com.pointbase.net.netJDBCPreparedStatement.executeUpdate(Unknown Source)
     at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:94)
     at yellowpages.ejb.DirectoryItem.DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.__WL_create(DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.java:3177)
     at yellowpages.ejb.DirectoryItem.DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.ejbPostCreate(DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.java:3094)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.ejb20.manager.DBManager.create(DBManager.java:1151)
     at weblogic.ejb20.manager.DBManager.localCreate(DBManager.java:1100)
     at weblogic.ejb20.internal.EntityEJBLocalHome.create(EntityEJBLocalHome.java:171)
     at yellowpages.ejb.DirectoryItem.DirectoryItem_lh4yf1_LocalHomeImpl.create(DirectoryItem_lh4yf1_LocalHomeImpl.java:94)
     at yellowpages.web.controller.AddEntryAction.execute(Unknown Source)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
; nested exception is: java.sql.SQLException: Data exception -- null value not allowed. .
java.sql.SQLException: Data exception -- null value not allowed. .
     at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown Source)
     at com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
     at com.pointbase.net.netJDBCPreparedStatement.executeUpdate(Unknown Source)
     at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:94)
     at yellowpages.ejb.DirectoryItem.DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.__WL_create(DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.java:3177)
     at yellowpages.ejb.DirectoryItem.DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.ejbPostCreate(DirectoryItem_lh4yf1__WebLogic_CMP_RDBMS.java:3094)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.ejb20.manager.DBManager.create(DBManager.java:1151)
     at weblogic.ejb20.manager.DBManager.localCreate(DBManager.java:1100)
     at weblogic.ejb20.internal.EntityEJBLocalHome.create(EntityEJBLocalHome.java:171)
     at yellowpages.ejb.DirectoryItem.DirectoryItem_lh4yf1_LocalHomeImpl.create(DirectoryItem_lh4yf1_LocalHomeImpl.java:94)
     at yellowpages.web.controller.AddEntryAction.execute(Unknown Source)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

I am not sure whether I understand your question.
The 'NamedSequenceTable' method is independent of data base type.
<from-docs>
Create a table named SEQUENCE to hold the current primary key value. The
table consists of a single row with a single column, as defined by the
following statement:
CREATE table_name (SEQUENCE int)
INSERT into table_name VALUES (0)
</from-docs>
Then, you can add the following in the DD -
<automatic-key-generation>
<generator-type>NamedSequenceTable</generator-type>
<generator_name>table_name</generator-name>
<key-cache-size>100</key-cache-size>
</automatic-key-generation>
The PK type should be set to java.lang.Integer or java.lang.Long
--Sathish
<Panduranga Swamy> wrote in message news:[email protected]..
Hi,
With named sequecne table,I am able to develop the application. What I
wanted is Say Table 1 having Identity column as Primary key in the table
Pointbase database.
With Automatic primary key generation in Deployment descriptor, We
generally specify SQL_SERVER or Named Sequencetable for Primary key
generation.
For pointbase database, I dont know how to configure this?
Could you help me in this regard,
Thanks,
Pandu

Generate primary key automatically

Similar Messages

Maybe you are looking for