Le 1/07/2010 17:12, Sam Mason a écrit :
On Thu, Jul 01, 2010 at 04:53:51PM +0200, Arnaud Lesauvage wrote:
Le 1/07/2010 16:48, Sam Mason a écrit :
How about using the built in character conversion routines. Something
like:
col = convert_from(convert_to(col, 'LATIN9'),'LATIN9')
as the
On Thu, Jul 01, 2010 at 04:53:51PM +0200, Arnaud Lesauvage wrote:
> Le 1/07/2010 16:48, Sam Mason a écrit :
>> How about using the built in character conversion routines. Something
>> like:
>>
>>col = convert_from(convert_to(col, 'LATIN9'),'LATIN9')
>>
>> as the check constraint, or its invers
Le 1/07/2010 16:48, Sam Mason a écrit :
On Tue, Jun 29, 2010 at 04:52:22PM +0200, Arnaud Lesauvage wrote:
We have a database in UTF8, from which we have to export text files in
LATIN9 encoding (or WIN1252, which is almostthe same I believe).
Records are entered via MSAccess forms (on psqlodb
On Tue, Jun 29, 2010 at 04:52:22PM +0200, Arnaud Lesauvage wrote:
> We have a database in UTF8, from which we have to export text files in
> LATIN9 encoding (or WIN1252, which is almostthe same I believe).
>
> Records are entered via MSAccess forms (on psqlodbc-linked tables).
> The problem is th
Le 30/06/2010 2:42, Howard Rogers a écrit :
Something I do in Oracle: do a TRANSLATE on whatever string is being
supplied, converting matching characters to spaces, and measure the length.
If the length is greater than zero, your supplied string has something in it
you're not expecting, at which
Hi list !
We have a database in UTF8, from which we have to export text files in
LATIN9 encoding (or WIN1252, which is almostthe same I believe).
Records are entered via MSAccess forms (on psqlodbc-linked tables).
The problem is that some of the characters input by the users have no
equivalen
