Schema issues
OK, we need all the interfaces to properly handle schemas within the
next month. However, we don't have psql working properly yet. Once we
get psql working, we can show examples of the changes we made and the
other interfaces can use that as a model.
Is anyone working on schema fixes for psql?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK, we need all the interfaces to properly handle schemas within the
next month. However, we don't have psql working properly yet. Once we
get psql working, we can show examples of the changes we made and the
other interfaces can use that as a model.Is anyone working on schema fixes for psql?
Yes, I did a lot of work on this, but got stuck on the whole
current_schemas problem, which apparently will need some
backend-to-sqlfunction mojo to fix. I'll clean up what I already have
and try to submit it next week in anticipation of that last missing
piece.
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200208021015
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9SpfRvJuQZxSWSsgRAituAJ9t5rFarCQoylBq/467vmALSue9dACg2hxg
GYQWUuPB2uUAxdCismtyOXc=
=eLjg
-----END PGP SIGNATURE-----
Import Notes
Resolved by subject fallback