From: | "Brian Schroeder" <bjswm(at)hotmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Relation does not exist |
Date: | 2002-05-12 23:30:19 |
Message-ID: | F66UtI9dm5UxP9Fekza0001290f@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Yes, putting the extra " in as Tom suggested has fixed it.
Thankyou.
>From: "Brian Schroeder" <bjswm(at)hotmail(dot)com>
>
>Thanks Tom, April for your help.
>
>As soon as I get the chance in the next few days I will look into
>your suggestions.
>
>Brian.
>
>>From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>>April L <april(at)i-netco(dot)com> writes:
>> > in your queries you have to refer to it with propercase and enclose in
>>"
>> > quotes
>> > so books_bookid_seq will cause the error
>> > "Books_BookID_seq" will be ok...
>>
>>It's been awhile, but I think that 7.0's nextval() would take the given
>>string literally, while later versions follow the downcase-unless-quoted
>>rule that applies to names in normal query contexts. So if you had
>> nextval('Books_BookID_seq')
>>before, you now need
>> nextval('"Books_BookID_seq"')
>>
>>Or you could recreate the sequence with an all-lower-case name...
>>
>> regards, tom lane
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew McMillan | 2002-05-12 23:32:21 | Re: newbie: Column CHECK(col contains '@') ? |
Previous Message | john-paul delaney | 2002-05-12 23:21:05 | Re: newbie: Column CHECK(col contains '@') ? |