Dirk Zoettl wrote:
> first of all for doing arithmetics the column type of > Pos has to bee changed. Replace "Pos LONG NOT NULL," > by "Pos FIXED(5) NOT NULL," . I do not think that Tilmann was able to create a table with a long column as primary key. Therefore I think, LONG was a misspelling in the mail. If not, I would like to know. With Dirk I agree, that integer values should be put into numeric columns--> If you want to input 1, use smallint/integer/fixed/decimal, no char/long. > There is another option to circumvent this bug > - quote your column name, example: > UPDATE BestAss SET Pos=-Pos WHERE "Pos" >=1 > > Sincerely, > Dirk Zoettl > > P.S: To avoid conflicts with reserved names I propose to > always use quoting of column and table names, since > the list of reserved words in quite large and is > database specific. Yes, double-quotes are the other chance. But if you do not want to use them everywhere, for example, you created the table without double-quotes, then "POS" is the only chance, because simple identifier are always changed to capital letters implicitly. Elke SAP Labs Berlin ____________________________________________________________ > > "Zabach, Elke" wrote: > > > [...snip...] > > > > Oh noooo! > > Sorry, it's my fault. > > There is an internally used syntax construct starting with > WHERE POS OF > > in the code. > > And now the stupid code does not realize that pos in your > case ist not the > > POS mentioned above, but a normal columnname. > > Thank you for reporting. I will fix it. > > > > In the meantime there are two choices > > - rename pos to something else > > - use WHERE 1<=pos > > > [...snip...] > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
