Re: Migrations encoding
Re: Migrations encoding
- Subject: Re: Migrations encoding
- From: Jon Nolan <email@hidden>
- Date: Fri, 12 Jun 2009 11:34:41 -0600
- Organization: Loch Garman
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden