Hi,
Thank You for such a great product. I had some problems with the
build, the configue script wasn't picking up the GNU readline library(I
compiled from source). I went online and saw many people were having the
same issue as I did. I looked @ the configure script and realised my
problem
Tom,
Thanks for the response.
The tables were created from the output from the previous release pg_dump
program, which omitted the double quotes in the DEFAULT nextval() clause.
I have tested the new version of pg_dump which includes them if the sequence
name contain mixed case characters.
Reg
Both Tom Lane & Stephan Szabo have pointed out that I should use a trigger
for my needs (and I will). Hopefully that will work for me in my
case. Good to know the NULL bug will be fixed in the next version, even if
I won't be needing it.
Thanks, as always, for the quick turnaround.
- Kristof
Thomas Piszczek ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
bug when using between or <= on varchar fields
Long Description
I just recognized that when using between or <= and >= on varchar fields postgresql
behaves quite s
On Tue, 19 Nov 2002 [EMAIL PROTECTED] wrote:
> Thomas Piszczek ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> bug when using between or <= on varchar fields
>
> Long Description
> I just recognized that when using betwee
