Re: bad systable on SE 5.0

On Thu, 25 Jun 1998 18:49:49 GMT, davek@summitdata.com (David Kosenko) wrote: >axsander@okay.net (Axel Sander) offerred: >+BTW, I think, an update of the tabid >+in systables is not possible, cause this is a "serial" field ? I > >You can update a serial field via sql. > The only thing a serial field by itself does >for you is to provide an automatically sequenced domain when you insert a record into >the table with a value of 0 for that field. All other operations are the same as on >any integer field. Now, if you built a unique index on it, or applied any other sort >of constraint, there may be some limitations as to what can be done with a serial >field. But a serial in of itself has no inherent limitations along those lines. They do. I allways got the following error message when trying: -232 A SERIAL column column-name may not be updated. You cannot alter the contents of a column with the SERIAL data type in the UPDATE statement, even when the updating value is zero. (You can specify a value of zero for a serial column when you use the INSERT statement; the database server ignores the zero and inserts a generated number.) Revise the statement so that only nonserial columns are updated. Somewhat irritating but still true. This is true even if there is no index, no primary key nor any other kinds of restraints spesified, just the serial field. Nils Myklebust NM Data AS Norway E-mail: Nils.Myklebust@nmdata.com FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html (Now with ODBC info under "Third party products".)