pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
To: Julian North <julian@mulberryst.co.uk>
Cc: pgsql-sql@postgresql.org
Subject: Re: naming conventions constraint
Date: Fri, 24 Oct 2003 14:01:24 -0400
Message-ID: <1067018483.81651.58.camel@jester> (raw)
In-Reply-To: <001901c399a4$92145c40$0401a8c0@ANYAKA>
References: <001901c399a4$92145c40$0401a8c0@ANYAKA>

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@postgresql.org)
> 

Attachments:

  signature.asc (application/pgp-signature, 186B) download

view thread (3+ messages)  latest in thread

Message-ID: <1067018483.81651.58.camel@jester>
Permalink:  ../1067018483.81651.58.camel@jester/
Also on:    postgresql.org/message-id/1067018483.81651.58.camel@jester

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: rbt@rbt.ca, julian@mulberryst.co.uk
  Subject: Re: naming conventions constraint
  In-Reply-To: <1067018483.81651.58.camel@jester>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox