在DBMS和表中使用i18n'ed字符集 [英] i18n'ed Character Set in DBMS and tables
问题描述
..你能为特定的表定义字符集而不是
数据库吗？
。哪些DBMS会让你这样做？
。你如何从输入中存储DBMS i18n''ed用户'，来自网上（基本上来自各地）
存储它并正确地提供它
返回用户，。 。 。$
。你能指点我这方面的信息吗？
我最好使用Java / JDBC驱动程序。
.. Can you define the Character Set for particular tables instead of
databases?
. Which DBMSs would let you do that?
. How do you store in a DBMS i18n''ed users'' from input, coming over
the web (basically from everywhere) store it and properly serve it
back to users, . . .?
. Can you point me to info on this?
I would preferably use Java/JDBC drivers.
推荐答案
Albretch写道：
Albretch wrote:
。你能为特定的表而不是数据库定义字符集吗？
是的，有时候在整个计算机科学领域，但由于你已经如此广泛地交叉发布了b $ b，你需要选择一个新闻组并询问再一次
的特定答案。
**。*哪些* DBMS *会*让*你*做那个？
这取决于。
**。*如何*你*存储*在* a * DBMS * i18n''ed *用户'* *来自网络（基本上来自各地）的网络（来自各地）存储它并正确地将其提供给用户，。 。 。？
. Can you define the Character Set for particular tables instead of
databases?
Yes, sometimes in the entire world of computer science, but since you have
cross-posted so widely, you need to choose a single newsgroup and ask again
for a specific answer.
**.*Which*DBMSs*would*let*you*do*that?
That depends.
**.*How*do*you*store*in*a*DBMS*i18n''ed*users''*fro m*input,*coming*over
the web (basically from everywhere) store it and properly serve it
back to users, . . .?
Unicode。选择一个新闻组，发一个帖子。
-
Paul Lutus
http://www.arachnoid.com
Unicode. Choose one newsgroup, make one post.
--
Paul Lutus
http://www.arachnoid.com
" Albretch" <磅***** @ hotmail.com>在消息中写道
news：f8 ************************** @ posting.google.c om ...
"Albretch" <lb*****@hotmail.com> wrote in message
news:f8**************************@posting.google.c om...
。你能为特定的表而不是
数据库定义字符集吗？
取决于DBMS。哪些DBMS会让你这样做？
各种各样。有了这么大的交叉点，任何人都可以用任何特定的DBMS回答问题。如何存储在DBMS中的i18n''ed用户'来自输入，来自网络（基本上来自各地）存储它并正确地将其提供给用户，。 。 。？
你不是。 I18n旨在允许您选择一种特定语言
并正确处理。存储和检索ALL语言，你使用
Unicode。 。你能指点我的信息吗？
www.unicode.org
我最好使用Java / JDBC驱动程序。
. Can you define the Character Set for particular tables instead of databases?
Depends on the DBMS . Which DBMSs would let you do that? Various. With such a massive crosspost, there''s little point in anybody''s
answering with any specific set of DBMS''s . How do you store in a DBMS i18n''ed users'' from input, coming over
the web (basically from everywhere) store it and properly serve it
back to users, . . .? You don''t. I18n is designed to permit you to SELECT ONE SPECIFIC language
and process that correctly. To store and retrieve "ALL" languages, you use
Unicode. . Can you point me to info on this? www.unicode.org
I would preferably use Java/JDBC drivers.
许多数据库都支持这些API。
Many databases support these APIs.
" Mark Yudkin" <我******** @ nospam.org>在消息新闻中写道：< ch ********** @ ngspool-d02.news.aol.com> ...
.. 。
"Mark Yudkin" <my***********************@nospam.org> wrote in message news:<ch**********@ngspool-d02.news.aol.com>...
.. . .
你不是。 I18n旨在允许您选择一种特定的语言
并正确处理。存储和检索ALL语言，你使用
Unicode。
You don''t. I18n is designed to permit you to SELECT ONE SPECIFIC language
and process that correctly. To store and retrieve "ALL" languages, you use
Unicode.
.. 。
好吧，我在那里看到''问题''。我认为你对它的态度是'/ b $ b''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
假设你可以将字符集和整理设置为
到列。现在，如果您使用unicode存储和检索
ALL语言''（正如你的建议），因为，自然而且每个SQL
ANSI'的spex，你只能设置一个字符集和一个相关的整理
专栏（和AFAIK（我可以理解为什么不是这样）你不能
当你用
$ b运行''select''查询时，动态指定/更改排序规则$ b a''order by''子句）
除非在Unicode中，我认为这是一个很好的技术示例
浪费试图保持广泛的ASCII''所有nat langs（这个
是我知道的最弱/最愚蠢的''标准'），整理不是
因为那里是字符集和整理之间的1 = 1地图
所有langs的订单对我来说听起来真的不自然
假设你有韩文名字和斯瓦希里语一张桌子，人们使用
unicode存储和检索ALL语言和''然后保持
指定字符集的额外列，。 。 。然后''选择
一个特定语言并正确处理''a la''：
SELECT SrName，来自NamesTable的FName
WHERE（CHAR_SET_Col =''Korean_CHAR_SET''）SORT BY SrName，FName;
和/或
SELECT SrName，FName来自NamesTable
WHERE（CHAR_SET_Col =''Swahili_CHAR_SET''）SORT BY SrName，FName;
这比两张桌子慢得多整理
敏感列设置为正确的char_set + collation对，
保留索引并定期对它们进行物理排序。
或？
.. . .
Well, I see ''issues'' right there. I think your approach to it is
wrong ''by design and implementation'' and this is what I am trying to
avoid.
Let''s say you can set the character set and collation all the way
down to the column. Now, if you ''use unicode to store and retrieve
"ALL" languages'' (as you suggest) and since, naturally and per SQL
ANSI''s spex, you can only set a character set and a related collation
on a column (and AFAIK (and I could see why it is not so) you can not
specify/change collation on the fly as you run a ''select'' query with
an ''order by'' clause)
Unless in Unicode, which by the way I see as a good technical example
of a waste by trying to keep extensively ASCII''ing all nat langs (this
is the weakest/silliest ''standard'' I know of), collation is not
necessary since there is a 1=1 map between character set and collation
orders for all langs which to me sounds really unnatural
Say you have Korean names and Swahili ones in a table, do people ''use
unicode to store and retrieve "ALL" languages and since'' and then keep
an extra columns specifying the character set, . . . and then ''SELECT
ONE SPECIFIC language and process that correctly'' a la'':
SELECT SrName, FName from NamesTable
WHERE(CHAR_SET_Col=''Korean_CHAR_SET'') SORT BY SrName, FName;
and/or
SELECT SrName, FName from NamesTable
WHERE(CHAR_SET_Col=''Swahili_CHAR_SET'') SORT BY SrName, FName;
this would be -way- slower than having the two tables collation
sensitive columns set to the correct char_set + collation pair,
keeping an index on them and periodically physically sorting them.
Or?
这篇关于在DBMS和表中使用i18n'ed字符集的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
