Discussion:
Encoding warning
Mark Lubratt
2006-09-28 21:20:28 UTC
Permalink
Hello!

I'm writing a little program for pgSQL4RB 1.01 (Mac OS X RB2006r2).
My database is using UTF8 encoding. When I start up the program, I'm
getting the following error:

Application ERROR: WARNING: Your database is defined to contain
text encoded in UTF8, however, this application is defined to use
UNICODE_UTF-8 instead. Making any modifications to your data may
corrupt your database!

My question is: Is this really an error? I read in the manual that
PostgreSQL prior to 7.3 and some encoding name reporting errors;
however, I'm using PostgreSQL 8.1.

I have numerous other databases that use UTF8 and I don't get this
error. Confusing...

Thanks!
Mark
Aliacta Support
2006-09-28 23:25:50 UTC
Permalink
Hi Mark,

This is a random bug that crept into the RB2005/2006 generations, it
doesn't occur with RB 5.1/5.5.

There's no real error with your database of course and it's a mystery
why this message pops up but here is a workaround that has been
if pgSQLerrorMessage.InStr("WARNING:") = 0 Then MsgBox pgSQLerrorMessage
This suppresses any warning messages, yet lets the real error message
come through.
Cheers,

Marc
Hello!
I'm writing a little program for pgSQL4RB 1.01 (Mac OS X RB2006r2).
My database is using UTF8 encoding. When I start up the program, I'm
Application ERROR: WARNING: Your database is defined to contain
text encoded in UTF8, however, this application is defined to use
UNICODE_UTF-8 instead. Making any modifications to your data may
corrupt your database!
My question is: Is this really an error? I read in the manual that
PostgreSQL prior to 7.3 and some encoding name reporting errors;
however, I'm using PostgreSQL 8.1.
I have numerous other databases that use UTF8 and I don't get this
error. Confusing..
Mark Lubratt
2006-09-29 04:36:12 UTC
Permalink
FYI. I got the error on my Mac OS X platform; but not on my Windows
platform.
Post by Aliacta Support
Hi Mark,
This is a random bug that crept into the RB2005/2006 generations, it
doesn't occur with RB 5.1/5.5.
There's no real error with your database of course and it's a mystery
why this message pops up but here is a workaround that has been
if pgSQLerrorMessage.InStr("WARNING:") = 0 Then MsgBox
pgSQLerrorMessage
This suppresses any warning messages, yet lets the real error message
come through.
Cheers,
Marc
Hello!
I'm writing a little program for pgSQL4RB 1.01 (Mac OS X RB2006r2).
My database is using UTF8 encoding. When I start up the program, I'm
Application ERROR: WARNING: Your database is defined to contain
text encoded in UTF8, however, this application is defined to use
UNICODE_UTF-8 instead. Making any modifications to your data may
corrupt your database!
My question is: Is this really an error? I read in the manual that
PostgreSQL prior to 7.3 and some encoding name reporting errors;
however, I'm using PostgreSQL 8.1.
I have numerous other databases that use UTF8 and I don't get this
error. Confusing..
_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com
m***@indeq.com
2006-09-29 00:21:52 UTC
Permalink
Thank you!

Mark
-------- Original Message --------
Subject: Re: [Aliacta PostgreSQL] Encoding warning
Date: Thu, September 28, 2006 6:25 pm
To: "Support Mailing List for Aliacta's PostgreSQL Related Products."
Hi Mark,
This is a random bug that crept into the RB2005/2006 generations, it
doesn't occur with RB 5.1/5.5.
There's no real error with your database of course and it's a mystery
why this message pops up but here is a workaround that has been
if pgSQLerrorMessage.InStr("WARNING:") = 0 Then MsgBox pgSQLerrorMessage
This suppresses any warning messages, yet lets the real error message
come through.
Cheers,
Marc
Hello!
I'm writing a little program for pgSQL4RB 1.01 (Mac OS X RB2006r2).
My database is using UTF8 encoding. When I start up the program, I'm
Application ERROR: WARNING: Your database is defined to contain
text encoded in UTF8, however, this application is defined to use
UNICODE_UTF-8 instead. Making any modifications to your data may
corrupt your database!
My question is: Is this really an error? I read in the manual that
PostgreSQL prior to 7.3 and some encoding name reporting errors;
however, I'm using PostgreSQL 8.1.
I have numerous other databases that use UTF8 and I don't get this
error. Confusing..
_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com
Loading...