Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

Thank you very much for your answer. El 26/07/15 a las 19:13, Ann Harrison aharri...@ibphoenix.com [firebird-support] escibió: On Sun, Jul 26, 2015 at 3:19 PM, Aldo Caruso aldo.car...@argencasas.com [firebird-support]

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

On Sun, Jul 26, 2015 at 3:19 PM, Aldo Caruso aldo.car...@argencasas.com [firebird-support] wrote: > > > > Why do you say that "All but SQL are now dead and BLR is an artifact > without benefit ?" > There is absolutely no interest in interoperability between database companies. Claiming to suppo

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

Thanks for your answer. I'm a bit confused by your two final phrases. Why do you say that "All but SQL are now dead and BLR is an artifact without benefit ?" And, if BLR doesn't include datatype information, why do you say that I have to recompile triggers and SP anyway ? Aldo El 26/07/15 a

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

> > > On 24-7-2015 21:37, Aldo Caruso aldo.car...@argencasas.com > [firebird-support] wrote: > > > I wonder if the following strategy has any pitfall: > > > > 1) Create the temporary field of the right character set > > 2) Fill it with data, using CAST to OCTETS as suggested by "The Firebird > > Bo

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

So, to be conservative, let's use the original process as recommended by the book. Thank you. El 25/07/15 a las 05:45, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] escibió: On 24-7-2015 21:37, Aldo Caruso aldo.car...@argencasas.com [firebird-support] wrote: > In the process of movin

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

On 24-7-2015 21:37, Aldo Caruso aldo.car...@argencasas.com [firebird-support] wrote: > In the process of moving the data back and forth, using a temporary > field of the right character set, you have to drop the original field an > then recreate it. > > The process of dropping a field is a bit nas

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

In the process of moving the data back and forth, using a temporary field of the right character set, you have to drop the original field an then recreate it. The process of dropping a field is a bit nasty because you have first to comment all the strored procedures and triggers in which this

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

Pretty clear. Thank you. El 23/07/15 a las 05:54, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] escibió: On Wed, 22 Jul 2015 21:09:12 -0300, "Aldo Caruso aldo.car...@argencasas.com [firebird-support]" wrote: > Raffaele, > > thanks for your answer. > The question is what prevents data

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

On Wed, 22 Jul 2015 21:09:12 -0300, "Aldo Caruso aldo.car...@argencasas.com [firebird-support]" wrote: > Raffaele, > > thanks for your answer. > The question is what prevents data loss in the first procedure ? > Suppose the filed in question is > > FIRST_NAME VARCHAR(60) CHAR

Re: Rif: [firebird-support] Chararacter set NONE to ISO8859_1

Raffaele, thanks for your answer. The question is what prevents data loss in the first procedure ? Suppose the filed in question is FIRST_NAME VARCHAR(60) CHARACTER SET NONE so lets create a temporary field TMP_NAME VARCHAR(60) CHARACATER SET ISO8859_1 and then let

Rif: [firebird-support] Chararacter set NONE to ISO8859_1

The first procedure provides you safe from data loss. you can directly execute the change of the charset after doing a complete backup of the database. ---Messaggio originale--- Da: Aldo Caruso aldo.car...@argencasas.com [firebird-support] Data: 21/07/2015 18.38.39 A: firebird-sup