Adrian,
I presume that hacking of the client image would be your preferred
solution as it is the single point of the problem and would against 10.x
as well as 9.x etc. Beside, editing the dbms parser to make CASE a
non-reserved word would potentially conflict with other sql clients of
the dbms that may use CASE correctly.
Which binary editor did you use as the hack should be straight forward?
Regards,
Ian

-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Ingres Forums
Sent: 03 February 2011 09:59
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] Using Reserved words as table names....

Hi,

Yes I had a couple of goes at global replace on the W4GL image file,
but it seems that W4GL is very sensative to change. (or I wasn't trying
hard enough with the binary editors)

We're on 9.3 Peter, to give us access to the II_WINSOCK2_NODELAY
parameter, which works wonders for the network perfomance.

The database is of a mangelable size so a move to 10 once everyone else
has found the bugs would be an activity measured in tens of minutes.

Thanks for your input, the binary edit of the parser to distract it
from the concept of 'case' was inspirational.

Biodiversity should be celebrated.

Adrian


--
Adrian Williamson
------------------------------------------------------------------------
Adrian Williamson's Profile:
http://community.ingres.com/forum/me...p?userid=11340
View this thread:
http://community.ingres.com/forum/sh...ad.php?t=12974

_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Hi,

I used an editor called to textpad, which will save the file as it
found it.

Using BeyondCompare to test the before and after edit of a W4GLV2 image
file verfied that the textpad editor had indeed only changed one
character in the test case I used.

However this modified file could not be interpreted by the W4GLV2
runtime enviroment, it started thrashing the CPU and stopped at the
first 'fetching' statement.

It was at this point that I came to the conclusion that the W4GLV2
image format might have some crafty checksum stuff going on.

Meanwhile we had recovered the correct development version for the
source, so I reverted to more traditional techniques for image
construction.

Thanks

Adrian


--
Adrian Williamson