On Sat, 2012-07-07 at 12:34 +0100, houmie wrote:
> # "local" is for Unix domain socket connections only
> local all all peer
>
> to
>
> # "local" is for Unix domain socket connections only
> local all all trust
>
>
> Is this the normal approach? Do I have to do the
Oh one more thing:
I have created a new superuser for postgre called django_user
Now when I try to connect to it it says:
FATAL: Peer authentication failed for user "django_user"
But the password is correct, I had no choice than change the settings
in /etc/postgresql/9.1/main/pg_hba.conf
Hi!
I personally find PostgreSQL much easier to work with. (and the docs
are beautiful)
MySQL has ugly docs, weird syntax, and it does unexpected strange
things. (and their terms of use is a little weird I think too.. yes
MySQL has burned me years ago and i've never forgiven it.)
-endofrant-
Thanks everybody for the encouragement.
Just to let you know you convinced me not giving up on postgresql.
It is actually quite nice that rules are tighter, to see right away what
might be wrong (e.g. field length etc)
Starting up with postgresql is much harder than MySQL, but then it
On 6-7-2012 17:56, Houmie wrote:
> The only reason I was considering postgresql was that some research
> suggested postgresql has much better support for changing Schemas along the
> way than MySQL.
There are many advantages for Postgresql and some for MySQL. But this
isn't a good reason to
On 12-07-06 8:56 AM, Houmie wrote:
Today I have started my first steps into postgresql, since its
recommended by the Django team.
I came across several issues, that I solved patiently one by one.
(disclaimer: I'm a Postgres homer)
These issues *should* come up with a well-designed database.
Today I have started my first steps into postgresql, since its recommended
by the Django team.
I came across several issues, that I solved patiently one by one.
1) Creating tables under postgresql requires to login as a different OS
login, from which you don't even know the password. Fine, I
7 matches
Mail list logo