If you define a database field like this with the "without time zone"
clause.
created timestamp(6) without time zone DEFAULT 'now' NOT NULL,
Then the current postgresql jdbc driver falls over in a heap when trying
to select and retrieve this field.
---(end of
I just checked out postgresql from CVS, built it and
did a pg_dumpall of my 7.1.3 databases.
When I try and load the data into 7.2 it gives
a bunch of errors like
\N command not found
I guess they are nulls and it can't recognise them
or something.
---(end of broadcast)-
>Chris Bitmead <[EMAIL PROTECTED]> writes:
>> ... I don't
>> like the old large object implementation, I need to store very large
>> numbers of objects and unless this implementation has changed
>> in recent times it won't cut it.
>
>Ha
>Use bytea, its for 0-255, binary data. When your client
>library does not support it, then base64 it in client side
>and later decode() into place.
Thanks, bytea sounds like what I need. Why no documentation on this
important data type?
Does the Java client library support setting this typ
Hi,
Now that postgresql doesn't have field size limits, it seems to
me they should be good for storing large blobs, even if it means
having to uuencode them to be non-binary or whatever. I don't
like the old large object implementation, I need to store very large
numbers of objects and unless thi
>It's relatively straightforward to allow check constraints to be inherited -
>but is it really possible to ever do the same with primary, unique or even
>foreign constraints?
You would either have to check each index in the hierarchy or else have
a single index across the whole hierarchy and
