I have a requirement that my authentication tables be stored in a
separate schema (within the same PostgreSQL database) to my science
data.  I can see that I can override RIFE's default names for
authentication parameters via config parameters TABLE_ROLE etc.  So I
think I can safely set this one to user_management.authrole, where
"user_management" is my schema name.  However, when I try this, RIFE
comes up with the error:

WARNING: Can't install the credentials database structure.; Error while
executing the SQL 'CREATE TABLE users.authrole (roleId INTEGER NOT NULL,
name VARCHAR(20) NOT NULL, CONSTRAINT USERS.AUTHROLE_PK PRIMARY KEY
(roleId), CONSTRAINT USERS.AUTHROLE_NAME_UQ UNIQUE (name))'.; ERROR:
syntax error at or near "."

What appears to have happened is that the derived constraints
USERS.AUTHROLE_PK and USERS.AUTHROLE_NAME_UQ don't have quotes round
them and the SQL query fails (I have verified that it works if I put
double quotes around these constraint names).  Is it possible some other
way (e.g. by multiple datasources) to achieve creation of authentication
tables in a Postgres schema that isn't "public" or some other default?
If multiple datasources is the way to go, please could someone point me
at an example?

Thanks,

David Herbert
British Antarctic Survey.

--  
This message (and any attachments) is for the recipient only.  NERC is subject
to the Freedom of Information Act 2000 and the contents of this email and any
reply you make may be disclosed by NERC unless it is exempt from release under
the Act.  Any material supplied to NERC may be stored in an electronic
records management system.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"rife-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to