Kolja Kleist wrote: > > Hello, > > I've got really strange problems with our production database(SAP DB > 7.4.3.32). > There is one table with the following columns: > > FOREIGN_KEY_TABLE_A, > FOREIGN_KEY_TABLE_B, > NUMBER_FIELD, > TEXT_FIELD > > First we had no primary key, but because of the bug as described here: > http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1129548 > > I created a primary key on the columns(FOREIGN_KEY_TABLE_A, > FOREIGN_KEY_TABLE_B) to drop the SYSKEY column. > Thus we have no problems with inserts anymore. > > But now, if I want to UPDATE the TEXT_FIELD column: > > UPDATE MyTable > SET NUMBER_FIELD = NULL, TEXT_FIELD = 'Foo' > WHERE FOREIGN_KEY_TABLE_A = x'0000000007C4C5DE' > AND FOREIGN_KEY_TABLE_B = x'0000000007A380C5' > > The following error occures: > 4005 - Unknown column name:SYSKEY > >
Please check your update-trigger for table MyTable. I assume there the old, now unknown, column SYSKEY is used inside. When DDL is done (renaming of columns, dropping columns, ...) one should check triggers if the old names/columns/tables are used inside and change the trigger accordingly. This is not done automatically (what should the kernel do with this trigger in this case???). Elke SAP Labs Berlin > Want can I do there? > > regards, > Kolja > > > -- > 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]
