-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > There is a SQL standard for this, and other DBMS look like they found a way > > How come it can not be done ? It *can* be done, but it won't be done. At least not by default. You might get better traction if you perhaps argue for a flag to pg_dump to exhibit the behavior you want. It has a small chance of being accepted, but a much greater chance than changing the default behavior. - -- Greg Sabino Mullane greg@xxxxxxxxxxxx End Point Corporation PGP Key: 0x14964AC8 200910251638 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkrkt2oACgkQvJuQZxSWSshyYwCcCRozshAfS22KtJJqoLmJdOsx X9IAmwYedkEyw819R6P0FZXVgskefaR4 =4oy5 -----END PGP SIGNATURE----- -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
