Hermann Himmelbauer wrote: > > Hi, > We are currently migrating our application from ADABAS-D 11 to MaxDB > (current > release). As MaxDB depends partially on ADABAS-D, this seems to be quite > simple. We access the database with Unix/Windows clients via ODBC. > > Now we have a problem with update statements. On ADABAS-D update > statements > which did not affect rows (= no rows are updated) produce no error, ODBC > returns then a "number of updated rows" of "0". > > MaxDB on the other hand produces an Error: > [MySQL MaxDB][LIBSQLOD SO] No rows updated or deleted, -3005 > Error number "-3005" is moreover not very specific, it applies to a number > of > database errors.
It sounds a little bit -- strange -- to receive error -3005 (invalid sql statement). There must be something quite unusual. Please provide the ODBC- and the kernel-version used and a vtrace according to http://sapdb.2scale.net/moin.cgi/VTrace where the -3005 can be found in. Elke SAP Labs Berlin > > Is there a way to tell MaxDB to behave like ADABAS-D and produce no error? > > Rewriting every update statements is inappropriate - first because our > client > is huge and this would cost a lot of time, moreover we lose compatibility > with ADABAS-D which we further need. > > We have an abstraction layer (C-library) which "translates" our own syntax > to > ODBC, so we could handle the error there but this is also not easy, as the > error is not distinct - if e.g. not an update but an delete produces this > error, it should not be caught, moreover the error number itself (-3005) > is > also not distinct, so we would have to compare the error string "No rows > updated or deleted" which is bad design as the error string could change > in > future MaxDB releases. > > Does anyone know a better solution to this problem? > > Best Regards, > Hermann Himmelbauer > > -- > [EMAIL PROTECTED] > GPG key ID: 299893C7 (on keyservers) > FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 > > -- > 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]
