Hello Herrmann, if 'the most other database systems' consists of Oracle, it would be possible convenient, but if you would have looked at e.g. MS-SQL and DB2, you would have found out that even the SEQUENCENAME.NEXTVAL notation is far from being common, not even speaking of the name of the NEXTVAL value when it occurs in a select list.
It can always considered dangerous to rely on the name generated for result pseudo columns that are the result of computed expressions. Explicit naming the column e.g. SELECT SEQUENCENAME.NEXTVAL AS NEXTVAL FROM DUAL is probably a better idea. Regards Alexander Schr�der SAP DB, SAP Labs Berlin > -----Original Message----- > From: Hermann Mundprecht [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 4:18 PM > To: [EMAIL PROTECTED] > Subject: Column name of NEXVAL from a sequence > > > Hi ! > > I would have a sugestion for the implementation of sequences in maxdb. > It would be convenient if the column alias of the value returned would > be NEXTVAL. > This is common in the most other db-systems that i know and > helps if you > are working with the DB with something like a java framework > that wraps > the call to the sequence and expects that the value is > returned with the > alias NEXTVAL. > > regards Hermann > -- > > Hermann Mundprecht > IT-Consultant > > Email: [EMAIL PROTECTED] > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
