On Sunday 2. March 2008, Swaminathan Saikumar wrote:
>I am using UTF8 Unicode for most of my data, but there is some data
> that I know for sure will be ASCII. However, this is also stored as
> UTF8, using up more space.
ASCII stored as UTF8 doesn't take up more space than plain ASCII, it's
exact
I didn't have proper knowledge about the UTF8 format, thanks.
I originally meant nvarchar & nchar, which is basically varchar & char that
supports Unicode regardless of the database encoding.
On 3/2/08, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
>
> Swaminathan Saikumar wrote:
> > I am familiar wi
Swaminathan Saikumar wrote:
I am familiar with MS Sql Server & just started using Postgres.
For storing Unicode, Sql Server uses nvarchar/char for unicode, and uses
char/varchar for ASCII.
Postgres has this encoding setting at the database level.
I am using UTF8 Unicode for most of my data, bu
Swaminathan Saikumar wrote:
I didn't have proper knowledge about the UTF8 format, thanks.
I originally meant nvarchar & nchar, which is basically varchar & char
that supports Unicode regardless of the database encoding.
Well, we don't need that when we have UTF8. There could be edge cases
spee
On Sun, Mar 02, 2008 at 11:50:01AM -0800,
Swaminathan Saikumar <[EMAIL PROTECTED]> wrote
a message of 30 lines which said:
> Postgres has this encoding setting at the database level.
Which is simpler, IMHO. "One encoding to rule them all"
> I am using UTF8 Unicode for most of my data, but the
