• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Troubleshooting utf8 text SQL generation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Troubleshooting utf8 text SQL generation


  • Subject: Re: Troubleshooting utf8 text SQL generation
  • From: Peter Vandoros <email@hidden>
  • Date: Sat, 14 Apr 2007 10:16:07 +1000

Hi Kieran,

If you are using TEXT and specified the charset to utf8, then you don't need to specify the valueType of E. Value type E is for databases that don't support UTF8 natively. If you change the valueType to something like S of c (not sure if this one is correct, check the documentation), then WO won't try to write/read the data as binary and convert it to a UTF8 String but instead it will write/read the data as a UTF8 String directly. This should solve your issue.

Keep in mind that you need to make sure that your JDBC URL is set to use that charset and unicode. See WebObjects wiki for more details on using MySQL with WO.

Regards

Peter

On 14/04/2007, at 4:58 AM, Kieran Kelleher wrote:

Hi guys, thanks for replies. The field is a type TEXT, so it does support encoding.... by chance I noticed the SQL was casting my search terms to _binary and that seems wrong.

On Apr 13, 2007, at 7:44 AM, Dev WO wrote:

Hello Kieran,

Someone will probably come up with an alternative, but I've never been to be able to make blob work the way I wanted with UTF-8. I had to convert my blob to mediumtext.
As far as I know (but I'm not a db expert;)) blob can't have an encoding like a mediumtext for example.


Xavier



I have a text blob attribute defined as
	External Type : TEXT
	Data Type : UTF Character Stream - String E

EOF is treating it as binary in the SQL generation, so I get this:
	... UPPER(T3.textobject) LIKE UPPER(_binary'%argentina%') ...

instead of this which is what I should expect??
	... UPPER(T3.textobject) LIKE UPPER(_utf8'%argentina%') ...


I am using MySQL. My connection string is: jdbc:mysql://localhost/omega?useUnicode=true&characterEncoding=UTF-8

and the table is defined as:
CREATE TABLE `textblob` (
  `oid` int(11) NOT NULL,
  `textobject` text,
  PRIMARY KEY  (`oid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Am I correct in thinking I should not be getting _binary before the search term?

-Kieran
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anazys.com


This email sent to email@hidden



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40etechgroup.com.au


This email sent to email@hidden

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
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


  • Follow-Ups:
    • Re: Troubleshooting utf8 text SQL generation
      • From: Kieran Kelleher <email@hidden>
References: 
 >Troubleshooting utf8 text SQL generation (From: Kieran Kelleher <email@hidden>)
 >Re: Troubleshooting utf8 text SQL generation (From: Dev WO <email@hidden>)
 >Re: Troubleshooting utf8 text SQL generation (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: Re: Type Number in WO WebServices
  • Next by Date: Re: Troubleshooting utf8 text SQL generation
  • Previous by thread: Re: Troubleshooting utf8 text SQL generation
  • Next by thread: Re: Troubleshooting utf8 text SQL generation
  • Index(es):
    • Date
    • Thread