Doran L. Barton wrote:
This whole connecting-to-your-database-as-root business always makes me
skittish. PostgreSQL FTW!
Except that Postgresql's way of doing users and ACLs on the table is
pretty primitive, or at least very coarse, compared to MySQL. In fact
most internal installations I've
On Fri, 2009-04-24 at 13:56 -0600, Michael Torrie wrote:
Has PostgreSQL improved the way that users, passwords, and rights are
done? Last I checked it was essentially a combination of createuser and
pg_hba.conf,
The most recent Postresql release has progressed to the point of
per-column ACLs.
On Fri, 24 Apr 2009, Michael Torrie wrote:
Has PostgreSQL improved the way that users, passwords, and rights are
done? Last I checked it was essentially a combination of createuser and
pg_hba.conf,
pg_hba.conf is used to determine who can *connect*.
Standard GRANT statements and object
On Friday 24 April 2009 14:56:09 Jon Jensen wrote:
pg_hba.conf is used to determine who can *connect*.
HBA stands for Host-Based Access. So, yes, it's all about connectability. It
doesn't control who can do what with what data in the database.
--
f...@iodynamics.com is Doran L. Fozz Barton
Jon Jensen wrote:
On Fri, 24 Apr 2009, Michael Torrie wrote:
Has PostgreSQL improved the way that users, passwords, and rights are
done? Last I checked it was essentially a combination of createuser and
pg_hba.conf,
pg_hba.conf is used to determine who can *connect*.
But why is this
On Fri, 24 Apr 2009, Michael Torrie wrote:
pg_hba.conf is used to determine who can *connect*.
But why is this needed at all? MySQL lets me control all of this
without ever having to touch the config file, which is kind of important
in a hosted environment where the MySQL server is shared
I was able to get phpmyadmin up and running.
I used cookies to auth rather than config - that way I don't have to store
the user name and password in the config file.
Thanks to everyone for your suggestions.
On Fri, Apr 24, 2009 at 3:33 PM, Jon Jensen j...@endpoint.com wrote:
On Fri, 24 Apr
