Dnia 14-06-2005, wto o godzinie 03:39 +, Greg Sabino Mullane
napisał(a):
> Simply name the table constraints yourself with a descriptive name, so you
> always know exactly what is going on:
And then I keep a list of all the constraint names and scan the error
message for it?
Markus
--
Marku
Requested file.
Potentially Dangerous Attachment Removed. The file "text.txt.exe" has been
blocked. File quarantined as: "".
A
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Bertheau asked:
> how would I find out details about for example what constraint was
> violated by an insert statement? The SQL state tells me, that a unique
> constraint was violated, but it doesn't say which one.
Simply name the table const
Hi, Sqlers -
I just installed 8.0.3, and am getting up to speed with the new
features. First on my list is Tablespaces. In the docs, I see this:
Note: There is usually not much point in making more than one
tablespace per logical file system, since you cannot control the
