On Tue, Jan 23, 2001 at 01:26:59PM +0200, Tomi Junnila wrote:
> * Santeri Paavolainen <[EMAIL PROTECTED]> wrote on 23.01.01 13:05:
> > >Fix:
> > SELECTs can be worked around with table aliases, others not.
>
> Oops, I forgot to include the cure. The first way to do this I encountered
> is to
* Santeri Paavolainen <[EMAIL PROTECTED]> wrote on 23.01.01 13:05:
> >Fix:
> SELECTs can be worked around with table aliases, others not.
Oops, I forgot to include the cure. The first way to do this I encountered
is to simply mysqldump the whole table into a text file, then search and
repla
* Santeri Paavolainen <[EMAIL PROTECTED]> wrote on 23.01.01 13:05:
> Using database created in 3.22 with a field named 'when'
> causes errors. For example,
When is a reserved word in 3.23. You're in for a nice little restructure...
(been there, done that :-( ).
--
Tomi Junnila <[EM
>Description:
Using database created in 3.22 with a field named 'when'
causes errors. For example,
SELECT when FROM atable;
will fail on syntax error. This works:
SELECT a.when FROM atable a;
However, since it's not (apparently) possi
