Michael Parker wrote:
> Ingo Freund wrote:
>
>>The system worked well with mySQL.
>
>
> WARNING: Bayes SQL does indeed work best with MySQL. Feel free to
> search the users/dev list in the past for more information.
>
>
That might be, but where should be the need to let two different
databas
Michael Parker schrieb:
> Ingo Freund wrote:
>
>>The system worked well with mySQL.
>
>
> WARNING: Bayes SQL does indeed work best with MySQL. Feel free to
> search the users/dev list in the past for more information.
>
>
>>Yes I followed the instructions.
>>Migrating to Postgres went through
Ingo Freund wrote:
>
> The system worked well with mySQL.
WARNING: Bayes SQL does indeed work best with MySQL. Feel free to
search the users/dev list in the past for more information.
> Yes I followed the instructions.
> Migrating to Postgres went through without any problems.
>
> This is what
Michael Parker wrote:
> Ingo Freund wrote:
>
>>Hi list,
>>
>>after my upgrade to spamassassin version 3.1.0
>>and migrate the database from mySQL to PostgreSQL there are
>>coming up many errors in the postgres logfile all like this:
>>
>>ERROR: operator does not exist: character = bytea
>>HINT:
Ingo Freund wrote:
> Hi list,
>
> after my upgrade to spamassassin version 3.1.0
> and migrate the database from mySQL to PostgreSQL there are
> coming up many errors in the postgres logfile all like this:
>
> ERROR: operator does not exist: character = bytea
> HINT: No operator matches the giv
Hi list,
after my upgrade to spamassassin version 3.1.0
and migrate the database from mySQL to PostgreSQL there are
coming up many errors in the postgres logfile all like this:
ERROR: operator does not exist: character = bytea
HINT: No operator matches the given name and argument type(s). You m
