You really should not rely on implicit assumptions in your code, such as 'the first value of an autoincrement field is 1'. If you use a different database, or different version of this one, that may be wrong and a nightmare to fix.
There are calls that will return the value of the field after it's inserted, you should use them instead. --- Andrew Shakinovsky <[EMAIL PROTECTED]> wrote: > Will the default value of an INTEGER PRIMARY KEY column always start > at > 1? > Example: > CREATE TABLE xyz (id INTEGER PRIMARY KEY); > INSERT INTO xyz VALUES (NULL); > > Will the value of the id column always be 1 in this example? I tried > numerous tests, and it seems to always start at 1, I wanted to just > make > sure this would always be the case before I start relying on it in my > code. > > ===== --------------------------------- "Lord Tarlington gazed upon the crazed Egyptian hieroglyphics on the walls of the ancient tomb of the petrified pharaoh, he vowed there would be no curse on him like on that other Lord, unless you count his marriage to Lady Tarlington who, when the lost treasure was found, will be dumped faster than that basket in the bulrushes." Melissa Rhodes --------------------------------- The Castles of Dereth Calendar: a tour of the art and architecture of Asheron's Call http://www.lulu.com/content/77264 __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
