Hi,

Same problem. I'm actually using a *.sql file within the Resources folder. It's been working great until I got to unicode characters.

I'm using this to call the *.sql. I've made sure that it is encoded (UTF-16). Also tried (UTF-8)

ERXJDBCUtilities.executeUpdateScriptFromResourceNamed(channel, "mysqltest.sql", null);

I tried changing the name to "name". Works fine until I introduce unicode characters.

Somewhere between reading the file to execution, the encoding is not right.

This is what ends up in the database:

Belgium/België/Belgique

Thanks


On Jun 12, 2009, at 10:34 AM, Jon Nolan wrote:

Tusker wrote:
I changed the file to be UTF-16 but I get an error now. I use the same sql file and manually run it in frontbase, it works. Example of the statement:

update Country set name = 'Belgium/België/Belgique' where country_id = 2;

"name" is a reserved word in Frontbase although FBManager (not sure about sql92) can often/usually/always handle non-quoted reserved words depending on how you're using them. I've always had to double- quote reserved words when working in Migrations though. i.e.

ERXJDBCUtilities.executeUpdate(database.adaptorChannel(), "update SITE set \"TYPE\" = 1 where \"TYPE\" = 10");


Of course it might still be an encoding issue but let's rule out this potential problem first. Try..


update Country set "name" = 'Belgium/België/Belgique' where country_id = 2;
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/tusker%40me.com

This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to