Yes I agree. The pre-built postgresql 7.4 supports UNICODE. My question is how to interpret the part of the Dspace installation doc quoted below:
http://dspace.org/technology/system-docs/install.html "Unicode (specifically UTF-8) support must be enabled. This is enabled by default in 8.0+. For 7.x, be sure to compile with the following options to the 'configure' script: --enable-multibyte --enable-unicode --with-java" I compared postgresql doc 7.4 and 8.2 at: http://www.postgresql.org/docs/7.4/interactive/multibyte.html and http://www.postgresql.org/docs/8.2/interactive/multibyte.html The difference is that in 7.4 "If no -E or --encoding option is given, SQL_ASCII is used." But in 8.2 "If no -E or --encoding option is given, initdb attempts to determine the appropriate encoding to use based on the specified or default locale." My interpretation is that the pre-built 7.4 RPM does not automatically create all database with UNICODE by default, that may be the reason why the dspace installation doc asks us to re-compile from the source. But then the installation doc also override this by specifying -E UNICODE when create the dspace database so this should not be a problem. Perhaps this is just an insurance policy in case someone writes a dpsace extension, creates another database but forgets to add the encoding. If that's the case, initdb with -E UNICODE is all I need because "initdb defines the default character set for a PostgreSQL cluster". Even for version 8.x, what if my default locale is US English but I still want the UNICODE database? I guess in any case initdb or createdb with -E UNICODE is the way to go regardless of the postgresql version, and re-compiling from source does not seem necessary. If that's the case, I think the dspace installation doc can use a bit clarification on this. Apology if I'm stating the obvious. Zhiwu Xie -----Original Message----- From: Jim Downing [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 5:27 AM To: Zhiwu Xie; [email protected] Subject: Re: [Dspace-tech] install postgresql 7.4 without compiling? Hi Zhiwu Xie, Zhiwu Xie wrote: > A newbie question: > > I'm installing Dspace on a minimum installation of CentOS 4.4. The > installation doc says: > > "Unicode (specifically UTF-8) support must be enabled. This is > enabled by default in 8.0+. For 7.x, be sure to compile with the > following options to the 'configure' script: > --enable-multibyte --enable-unicode --with-java " > > Since I can easily yum the postgresql 7.4 I wanted to avoid compiling > from source. My later admin work can be a lot easier if I yum install > postgresql. If the --enable-unicode is just to enable using Unicode in > the database, can I just add -E UNICODE when I do initdb? The > --with-java option is to build the jdbc, which I can also easily yum. > I'd be surprised if the packaged postgresql didn't already have unicode support, in which case you'll be able to specify the encoding when you createdb. Best regards, jim ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
