Sven K�hler wrote: > >>while developing with SAPDB i sometimes stare on my screen and read > >>error message like > >> "Syntax error or access violation;-3005 POS(1) Invalid SQL > >>statement." > >>This error-message was produced because an INSERT statement didn't > >>define a value for a column that was defined to be "NOT NULL". > > > > > > Oops, how did you manage this ? Usually SAP DB is a little > bit more precise. > > Would you mind telling us which client you are using and > perhaps provide > > a vtrace of the commands send to the kernel ? > > for description of vtrace-preparartion please see: > > http://sapdb.2scale.net/moin.cgi/VTrace > > i already read the mail from daniel, but just in case you need to > reproduce this: > > create table test(id int default serial, text1 varchar(255), text2 > varchar(255) not null) > // > insert into test(text1, text2) values (null, 'asdf') > // > insert into test(text1) values (null) > > > first insert doesn't fail > second failes >
�rchgz, sh... (4 letter word), such a stupid bug. It only occurs if a serial-column is in the table and one of some special errors occurs. Then the original error is lost and that stupid one is sent back. Thank you for reporting, will of course be fixed. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
