the version of mysql I’ve been developing against hasn’t been enforcing
reserved words. Just after the release of Alpha 1, I started to redo some of
them. Somehow Transaction->Data didn’t make it onto my list. It should
be fixed the next time I get a few moments.
Thanks for the bugreport,
-jOn Mon, Sep 18, 2000 at 10:55:49AM +0200, Frans Stekelenburg wrote:
A MySQL user question about RT…:
At some point the data model and source has been changed so that the
’Transactions’ table now
requires a row ‘Data’. Our MySQL (Ver 6.2 Distrib 3.22.21, for
refuses this fieldname, likely cause it’s an internal one.
Thereby, now all through the code one sees ‘Data’ beeing used, but it
seems not allways
for the same purpose/data type, which makes it VERY confusing and hard
to follow the source code.
We labeled the tablefield Transactions->Data1 (instead of Data), and
tried to figure out which Data in the code to change to Data1 to make it
work. It works (partly) now, but I’m bot sure that we got 'em all…
Probably your MySQL didn’t complain about ‘Data’?
Still, can you address this matter?
Acriter, the Netherlands
jesse reed vincent — firstname.lastname@example.org — email@example.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
"Bother," said Pooh, “Eeyore, ready two photon torpedoes and lock
phasers on the Heffalump, Piglet, meet me in transporter room three”