Just to add some clarity to the Dawid's fine comments: On 4/14/05, Dawid Kuroczko <qnex42@xxxxxxxxx> wrote: > On 4/13/05, Matt Van Mater <matt.vanmater@xxxxxxxxx> wrote: > I believe that COPY handles things like unique constraints and > referer integerity just fine (of the latter I am not sure) -- well, > its hard to imagine PostgreSQL allowing itself to loose integrity > of the data, don't you agree? > I do, and so does PG. :) Everything that would normally happen with an INSERT, including firing TRIGGERs, checking FKEYs, setting DEFAULTs, running CHECK constraints -- everything -- happens with a COPY import. The *one and only* exception to the above statement is that RULEs to not get used on COPY. The reason for this is that RULEs rewrite queries and after the COPY FROM header there isn't a query to rewrite, it's just a pile of data. This is in the docs, but it's not easy to find. It's actually just one line in the "Notes" section of http://www.postgresql.org/docs/8.0/static/sql-copy.html . Perhaps we should add some more verbiage (he says, non-voluntarily...)? -- Mike Rylander mrylander@xxxxxxxxx GPLS -- PINES Development Database Developer http://open-ils.org ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
