Re: naming conventions constraint

thats just what i needed to know.

many many thanks!

j.

-----Original Message-----
From: Rod Taylor [mailto:rbt(at)rbt(dot)ca]
Sent: 24 October 2003 19:01
To: Julian North
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: naming conventions constraint

rbt=# create table bob_is(your_uncle integer, constraint
"bob_is#your_uncle" check(true));
CREATE TABLE
rbt=# \d bob_is
Table "public.bob_is"
Column | Type | Modifiers
------------+---------+-----------
your_uncle | integer |
Check constraints:
"bob_is#your_uncle" CHECK true

You need to quote strings which contain special characters.

On Thu, 2003-10-23 at 16:30, Julian North wrote:
> I'm at the very beginning of working with postgres.
>
> The aim is to replace / build a number of very large and very complex
> database currently residing in Oracle, MSSQL and Informix.
>
> In order to coordinate across a medium size DBA team I instituted a
standard
> constraint naming convention suitable for the above 3 platforms.
>
> For example a foreign key would be FK_table#reftable#column.
>
> Unfortunately I don't appear to be able to use it with postgres.
>
> This is because I can't use the # character in constraint names.
>
> Does anybody have any suggestions as to an alternative that is also a
single
> char? (I'm limited to 30 chars cos of oracle and manyof the current names
at
> the limit).
>
> Any help appreciated,
>
>
>
> Julian.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>