Adriano, thank you for your reply.

The problem is that in my post I was just describing a test-case. In
reality we are talking about 30 production databases each with around
3500 procedures and 1000 triggers.

If I understood you well, you are proposing to drop and recreate all
this procedures and triggers using a connection character set like
ISO8859_1? I thought that the procedure rdb$fix_metadata would fix the
problem? Won't we be able to upgrade to 2.5 without recreation of our
procs and triggers?

Thanks again.

--- In firebird-support@yahoogroups.com, Adriano dos Santos Fernandes
<adrianosf@...> wrote:

>
> Stefan Sinne escreveu:
> > _______________ script start _______________________________
> > SET SQL DIALECT 3;
> > SET NAMES NONE;
> >
> This is the reason. You're using connection charset NONE and conversion
> to UNICODE_FSS doesn't happen. In v2.5, the CREATE PROCEDURE will fail
> with "Malformed string" error.
>
> > CREATE DATABASE 'LOCALHOST:d:\database\prueba.fdb'
> > USER 'SYSDBA' PASSWORD 'masterkey'
> > PAGE_SIZE 4096
> > DEFAULT CHARACTER SET NONE;
> >
> > SET TERM ^ ;
> > CREATE PROCEDURE NEW_PROCEDURE
> > AS
> > begin
> > /* Some special (spanish) chars: ñѺªáÁéÉíÍóÓúÚ */
> > exit;
> > end
> > ^
> > SET TERM ; ^
> > _______________ script end _______________________________
> >
> Use a connection charset that matches the characters you're using.
>
>
> Adriano
>