This is because your database is in UTF8 format. As a result SA cannot
read it (though it can write it).
Drop the database and recreate it and the tables in latin and it will
work just fine. You will have to retrain after that though.
-Original Message-
From: Hamish Marson [mailto:[EMAI
On Tue, 08 Aug 2006 12:08:52 +0100, Hamish Marson
<[EMAIL PROTECTED]> wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Nigel Frankcom wrote:
>> I'm not sure what you've done there, I didn't realise it was
>> possible to mix collation types in the same table. Have you checked
>> that all t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Frankcom wrote:
> I'm not sure what you've done there, I didn't realise it was
> possible to mix collation types in the same table. Have you checked
> that all tables are the same type? MyISAM or Inno? If they are all
> the same, I'd be inclined
On Tue, 08 Aug 2006 12:02:04 +0100, Hamish Marson
<[EMAIL PROTECTED]> wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Nigel Frankcom wrote:
>> I'm not sure what you've done there, I didn't realise it was
>> possible to mix collation types in the same table. Have you checked
>> that all t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Frankcom wrote:
> I'm not sure what you've done there, I didn't realise it was
> possible to mix collation types in the same table. Have you checked
> that all tables are the same type? MyISAM or Inno? If they are all
> the same, I'd be inclined
I'm not sure what you've done there, I didn't realise it was possible
to mix collation types in the same table. Have you checked that all
tables are the same type? MyISAM or Inno? If they are all the same,
I'd be inclined to pull it down, rebuild from the SA supplied SQL and
retrain.
Did you merge
