example db -- SQL Query broken because of NEW reserved words

[Ruslan Zasukhin]

On 11/2/08 4:30 PM, "jda" <jda at his.com> wrote:

>>> Unfortunately, I construct sql queries in hundreds of locations in my
>>> code, and can't possibly be sure that I've tracked them all down -- I
>>> have over 10K users, and I don't want to risk distributing buggy
>>> software. I'll go back to 4b2.
>> 
>> But you need solve issue and again try b7 or newer, right ?
>> 
>> 
>> IMO its easy in RB to find all places where PAGES word present.
>> 
> 
> As I told Ivan, my users can create their own sql searches, and
> 'pages' is natural for a database on books. I remind you that my users
> as not computer IT people, they are students, doctors, scientists,
> teachers. Telling them to put pages in brackets ([pages]) isn't very
> friendly. I hate it when code breaks. So I won't upgrade unless there
> is some bug fix you make that I have to have.

If word pages is inside of literals

    WHERE fld = 'pages'             NO PROBLEMS

So USER searches are not affected by this.


Affected are only queries that YOU make, where you mention your FIELD with
name PAGES.

    WHERE pages = 5

And you can easy get such queries working using []

    WHERE [pages] = 5

    

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]