Egg in the face time. I knew it was going to be one of those...
CREATE ROLE --DOES NOT EQUAL-- CREATE USER
Whereas the latter implies LOGIN priv, the former does not.
I'd read about LOGIN auto-implied some time ago, but I'd not noticed
that is not so w/ a created ROLE.
Maybe you can sme
Ralph Smith <[EMAIL PROTECTED]> writes:
> However I'm now trying to access it using all lower case.
> Are you saying that IT'S confused and I should go all lower or use
> quotes (") not (')?
Well, you can do it either way.
If you want the database to be really truly named "LabNews_dev"
(mixed c
On Apr 4, 2008, at 2:11 PM, Tom Lane wrote:
---
Ralph Smith <[EMAIL PROTECTED]> writes:
I just can't connect to a database, though I can to others as other
users...
You'
Ralph Smith <[EMAIL PROTECTED]> writes:
> I just can't connect to a database, though I can to others as other
> users...
You're confused about the rules for case sensitivity.
> postgres=# CREATE DATABASE LabNews_dev WITH OWNER=xyz ENCODING='UTF8' ;
> CREATE DATABASE
This got folded to lower ca
I just can't connect to a database, though I can to others as other
users...
postgres=# CREATE ROLE xyz WITH password 'abc' ;
CREATE ROLE
postgres=# CREATE DATABASE LabNews_dev WITH OWNER=xyz ENCODING='UTF8' ;
CREATE DATABASE
postgres=# grant create, connect on database LabNews_dev to xyz wi
