On Sun, Sep 30, 2007 at 11:55:00AM +0800, CN wrote:
> Various people have various perceptions. I don't feel that my suggestion
> only serves to make PostgreSQL become a software product fitting only
> *myself*. On the contrary, I believe PostgreSQL will become suitable for
> more novice users if in
Hi,
Get a VPS - Virtual Private Server. Mine is 29$ and it is fine for 480MB
RAM and enough disk space. I am a full admin on my server, so I install
and configure Postgresql without problem.
YES! I agree that the default encoding must be UTF-8. I started using
Postgresql, cause I had problems w
On 09/30/07 10:31, brian wrote:
[snip]
>
> The default for MySQL is latin1 with swedish sorting.
Yorn desh born, der ritt de gitt der gue
Orn desh, dee born desh, de umn børk! børk! børk!
--
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and h
>>CN wrote:
> ... MyZql ... MyZql
>
> 1. "MyZql" is easier to pronounce and remember than "PostgreSQL".
Actually, that's *MySQL*.
> Yes, UNICODE results in poorer performance than SQL_ASCII. However, this
> is not a problem at all because advanced users will use "-E" when they
> only needs SQL_A
On Fri, 28 Sep 2007 21:32:43 -0400, "Carlos Moreno"
<[EMAIL PROTECTED]> said:
> CN wrote:
> > Hi!
> > "initdb" use SQL_ASCII as the default characterset encoding when it is
> > not given option "-E" and when it can not correctly derive one from
> > locale. I suggest "initdb" use UNICODE instead of
Ron Johnson wrote:
> On 09/28/07 21:12, Tom Lane wrote:
>> Michael Fuhr <[EMAIL PROTECTED]> writes:
>>> No, it isn't. If you get UTF8 (formerly UNICODE) as a default then
>>> it's because initdb is picking it up from your environment.
>> Which initdb has done since 8.0. If the OP is such a rabid
Michael Fuhr wrote:
On Fri, Sep 28, 2007 at 09:32:43PM -0400, Carlos Moreno wrote:
Oh, and BTW, welcome to version 8 of PostgreSQL ... The default
encoding for initdb is . Ta-d!!! Unicode !!!
No, it isn't. If you get UTF8 (formerly UNICODE) as a default then
it's because initd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/07 21:12, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
>> No, it isn't. If you get UTF8 (formerly UNICODE) as a default then
>> it's because initdb is picking it up from your environment.
>
> Which initdb has done since 8.0. I
Michael Fuhr <[EMAIL PROTECTED]> writes:
> No, it isn't. If you get UTF8 (formerly UNICODE) as a default then
> it's because initdb is picking it up from your environment.
Which initdb has done since 8.0. If the OP is such a rabid UTF8 fan,
one wonders why his default locale setting isn't using
On Fri, Sep 28, 2007 at 09:32:43PM -0400, Carlos Moreno wrote:
> Oh, and BTW, welcome to version 8 of PostgreSQL ... The default
> encoding for initdb is . Ta-d!!! Unicode !!!
No, it isn't. If you get UTF8 (formerly UNICODE) as a default then
it's because initdb is picking it up from your
CN wrote:
> Hi!
> "initdb" use SQL_ASCII as the default characterset encoding when it is
> not given option "-E" and when it can not correctly derive one from
> locale. I suggest "initdb" use UNICODE instead of SQL_ASCII because
> UNICODE is far more useful than SQL_ASCII.
>
> Not all webmasters ar
Hi!
"initdb" use SQL_ASCII as the default characterset encoding when it is
not given option "-E" and when it can not correctly derive one from
locale. I suggest "initdb" use UNICODE instead of SQL_ASCII because
UNICODE is far more useful than SQL_ASCII.
Not all webmasters are willing to spend time
12 matches
Mail list logo
