Dev Kumkar wrote:
Succeeds but as replied earlier it creates database with LC_COLLATE =
'English_United States.1252' which corresponds to Latin1.
Despite windows-1252 being a monobyte encoding sharing most
of LATIN1 codes and character set, it does not mean that
English_United
On Thu, Feb 20, 2014 at 4:34 PM, Daniel Verite dan...@manitou-mail.orgwrote:
Despite windows-1252 being a monobyte encoding sharing most
of LATIN1 codes and character set, it does not mean that
English_United States.1252 is limited to this character set.
You may use UTF-8 databases with that
On Thu, Feb 20, 2014 at 3:04 AM, Gavin Flower gavinflo...@archidevsys.co.nz
wrote:
Upgrade servers to Linux? :-P
Actually that's not the solution but running away from it.
There is a heavy footprint of customers and huge market on windows too and
so not that easy to migrate and convince in
On 21/02/14 02:04, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 3:04 AM, Gavin Flower
gavinflo...@archidevsys.co.nz mailto:gavinflo...@archidevsys.co.nz
wrote:
Upgrade servers to Linux? :-P
Actually that's not the solution but running away from it.
There is a heavy footprint of customers
On Fri, Feb 21, 2014 at 12:14 AM, Gavin Flower
gavinflo...@archidevsys.co.nz wrote:
On 21/02/14 02:04, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 3:04 AM, Gavin Flower
gavinflo...@archidevsys.co.nz wrote:
Upgrade servers to Linux? :-P
Actually that's not the solution but running
On 02/20/2014 11:40 AM, Dev Kumkar wrote:
Hmm. Don't want to digress here and loose the topic context.
Here would really appreciate if there are any suggestions for UTF-8
collation on Windows?
Well I dug out a Windows machine and tried to get what you wanted, to no
avail. As far as I know
On Fri, Feb 21, 2014 at 1:26 AM, Adrian Klaver adrian.kla...@aklaver.comwrote:
Well I dug out a Windows machine and tried to get what you wanted, to no
avail. As far as I know there is no UTF8 collation, it is an encoding. What
you want if I am following, is the en_US locale (or equivalent for
On 02/20/2014 11:40 AM, Dev Kumkar wrote:
Hmm. Don't want to digress here and loose the topic context.
Here would really appreciate if there are any suggestions for UTF-8
collation on Windows?
Just had idea, not sure how feasible it is in your situation though. Run
Postgres in a Linux VM
On 02/20/2014 12:27 PM, Dev Kumkar wrote:
On Fri, Feb 21, 2014 at 1:26 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
Well I dug out a Windows machine and tried to get what you wanted,
to no avail. As far as I know there is no UTF8 collation, it is
On 02/19/2014 06:41 AM, Dev Kumkar wrote:
Am really going no where with this after so many searching over net or
am missing some basic things, not sure!
What is the equivalent for en_US.UTF-8 collation in case of windows?
In Linux am creating database with following options, as follows:
-E
On Wed, Feb 19, 2014 at 10:16 PM, Adrian Klaver
adrian.kla...@aklaver.comwrote:
I found the below that might help. I do not use Windows much any more so I
do not have a machine handy to confirm.
http://www.g-loaded.eu/2011/02/27/locale-windows/
Thanks for the pointer. *american_usa* works
On 02/19/2014 11:42 AM, Dev Kumkar wrote:
On Wed, Feb 19, 2014 at 10:16 PM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
I found the below that might help. I do not use Windows much any
more so I do not have a machine handy to confirm.
On Thu, Feb 20, 2014 at 1:19 AM, Adrian Klaver adrian.kla...@aklaver.comwrote:
So what is the exact command you are using?
createdb -U postgres -E utf8 -l american_usa DBNAME
Above command fails to create utf-8 LC_COLLATE.
Regards...
On 02/19/2014 12:03 PM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 1:19 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
So what is the exact command you are using?
createdb -U postgres -E utf8 -l american_usa DBNAME
Above command fails to create utf-8
On Thu, Feb 20, 2014 at 1:41 AM, Adrian Klaver adrian.kla...@aklaver.comwrote:
What does it set LC_CTYPE to?
So what happens if you do?:
createdb -U postgres -E utf8 -l american_usa.65001 DBNAME
*createdb: database creation failed: ERROR: invalid locale name:
american_usa.65001 *
or
On 02/19/2014 12:16 PM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 1:41 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
What does it set LC_CTYPE to?
So what happens if you do?:
createdb -U postgres -E utf8 -l american_usa.65001 DBNAME
On Thu, Feb 20, 2014 at 2:01 AM, Adrian Klaver adrian.kla...@aklaver.comwrote:
Just noticed you are not specifying the template database. Try using
template0:
createdb -U postgres -E utf8 --lc-ctype=american_usa
--lc-collate=american_usa -T template0 DBNAME
Same result i.e. LC_COLLATE and
On 02/19/2014 12:43 PM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 2:01 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
Just noticed you are not specifying the template database. Try using
template0:
createdb -U postgres -E utf8
On Thu, Feb 20, 2014 at 2:24 AM, Adrian Klaver adrian.kla...@aklaver.comwrote:
Alright last shot:)
Taking hint from here:
http://msdn.microsoft.com/en-us/library/x99tb11d.aspx
try:
createdb -U postgres -E utf8 -l en-US DBNAME
If that does not work, not sure where to go.
This won't
On 02/19/2014 01:09 PM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 2:24 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
Alright last shot:)
Taking hint from here:
http://msdn.microsoft.com/en-__us/library/x99tb11d.aspx
On Thu, Feb 20, 2014 at 2:45 AM, Adrian Klaver adrian.kla...@aklaver.comwrote:
Have you tried it?
Note that the locale name is different then the one Linux.
On Linux it is en_US.
What I suggested is en-US.
Yes. Here is the output:
createdb -U postgres -E utf8 -l en-US -T template0
On 02/19/2014 01:21 PM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 2:45 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
Have you tried it?
Note that the locale name is different then the one Linux.
On Linux it is en_US.
What I suggested is
On 2/19/2014 1:21 PM, Dev Kumkar wrote:
createdb -U postgres -E utf8 -l en-US -T template0 mynewdb
Password:
*createdb: database creation failed: ERROR: invalid locale name: en-US*
I believe its en_US ... _ not -
--
john r pierce 37N 122W
somewhere
On 20/02/14 10:28, Adrian Klaver wrote:
On 02/19/2014 01:21 PM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 2:45 AM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
Have you tried it?
Note that the locale name is different then the one Linux.
On
On 02/19/2014 01:30 PM, John R Pierce wrote:
On 2/19/2014 1:21 PM, Dev Kumkar wrote:
createdb -U postgres -E utf8 -l en-US -T template0 mynewdb
Password:
*createdb: database creation failed: ERROR: invalid locale name: en-US*
I believe its en_US ... _ not -
Unfortunately this is a Windows
On 2/19/2014 1:35 PM, Adrian Klaver wrote:
Unfortunately this is a Windows install and that does not work either.
windows encodings are a pain. their Unicode is NOT utf8, its ucs2 aka
utf16. I just checked my default install of potsgres 9.2, it appears
its using WIN1252 encoding,
On Thu, Feb 20, 2014 at 3:17 AM, John R Pierce pie...@hogranch.com wrote:
On 2/19/2014 1:35 PM, Adrian Klaver wrote:
Unfortunately this is a Windows install and that does not work either.
windows encodings are a pain. their Unicode is NOT utf8, its ucs2 aka
utf16. I just checked my
27 matches
Mail list logo
