- Make sure your MS SQL Server tables use NCHAR, NVARCHAR, NTEXT column types for all string data that could contain unicode data.
- Make sure that your database driver is configured to send String parameters as unicode. Both JTds and MSFT drivers have jdbc url parameter called sendStringParametersAsUnicode that accepts TRUE or FALSE. The default for jTDS is TRUE. This generates the correct SQL for prepared statements.
- Make sure you use prepared statements as much as possible (WO seems to do that by default)
- Check your raw rows and JDBC queries for hard coded SQL that is not properly formatted for SQL server (i.e. The N syntax)
- Use EO Prototypes thru out your model. We have a large application (175 tables) - it would have taken forever to change the model by hand.
I did not have to build a custom plugin or make any modifications to our EOModel.
Thanks to everyone that made suggestions on helping me resolve the problem. I learned a bunch during the process.
--
Dov Rosenberg
Conviveon/Inquira
Knowledge Management Experts
http://www.conviveon.com
http://www.inquira.com
_______________________________________________ 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]
