Subject | Re: unicode & SP |
---|---|
Author | Gediminas |
Post date | 2004-01-20T13:42:16Z |
Thanks Helen for your answer - great info. Maybe do you have some
links/info about cursors in queries & etc - DB is not my region of
programming specialization, but see, that need to gain more knowledge ;)
store lithuanian characters without conversion error) - so set default
DB character set to Unicode_FSS. If I understood right, that to write
character sets in such scenario isn't neccessary
links/info about cursors in queries & etc - DB is not my region of
programming specialization, but see, that need to gain more knowledge ;)
> Problem B: You're trying to use multiple subqueries on the samecursor to
> derive multiple run-time fields - it doesn't work this way. Eitheruse a
> join between KOLEKTYVAI and ZMONES or define separate aliases for eachYes, I'm working with the unicode charset (as it's the only one can
> subquery
store lithuanian characters without conversion error) - so set default
DB character set to Unicode_FSS. If I understood right, that to write
character sets in such scenario isn't neccessary
> What is the unicode problem that the subject refers to? Are these
> unicode_fss columns? If so, you need to do this:
>
> CREATE PROCEDURE SP_SELECT_KOLEKTYVAI_SEARCH (
> PAVADINIMAS_IN VARCHAR (50) CHARACTER SET UNICODE_FSS,
> MIESTAS_IN VARCHAR (24) CHARACTER SET UNICODE_FSS)
> RETURNS (
> X1 VARCHAR(..) CHARACTER SET UNICODE_FSS,
> and so on...)