Bug in 3.23.33? Or design decision?

2001-03-07 Thread eric
Hi! I just upgraded from 3.22.26a to 3.23.33. We've got a database that has a table that has a column with the name: FullText. Unfortunately, now with 3.23.33, any queries that explicitly refer to this column/field return an SQL error. So far this has been tested with SELECT and

Re: Bug in 3.23.33? Or design decision?

2001-03-07 Thread Peter Skipworth
fulltext is now a reserved word - either change the name of the field, or use quotes when refering to it. regards, P On Tue, 6 Mar 2001 [EMAIL PROTECTED] wrote: Hi! I just upgraded from 3.22.26a to 3.23.33. We've got a database that has a table that has a column with the name:

Antwort: Bug in 3.23.33? Or design decision?

2001-03-07 Thread alexander . skwar
On 06.03.2001 19:05:34 iso-8859-1 wrote: Is this expected behavior? Or is this an actual bug? I suppose this may be expected behavior, as FullText now is a reserved word in MySQL - Before posting, please check: