Oliver Br�kerwrote: > 3) The SERIAL-Type > > It�s a nice type but of now worth. If you use this type as a primary > key, then access is not able to update linked-tables using this type. > Very sad, because in postgreSQL this is working correct. My > workaround > was to use a table for the next value for every auto-increment field. > This not a big problem, because the workaround is working properly.
Obviously you missed the message from Thomas (written in October) " >The other option is, to use DEFAULT SERIAL which was my favourite, until >i read, that i cannot get the value that was used. I would recommend datatype SERIAL, i.e. CREATE TABLE TEST (S SERIAL, ... >Is this solved in SAPDB 7.3? >Is a patch planned? With the next SAPDB version you can get the last serial value via the currval function specifying the table name, i.e. SELECT TEST.CURRVAL INTO ? FROM SYSDBA.DUAL; or easier in a db-procedure VAR currVal integer; currVal = TEST.CURRVAL; >Is it solved in v7.4? >when will it be released? 7.4 will have the same behavior. Thomas" The release 7.3.0.29 (available) and the release 7.4.3.10 (not available so far) include this. The privilege-problem mentioned yesterday will be solved in the release 7.3.0.29 / 7.4.3.10. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
