- 26 3月, 2002 8 次提交
-
-
由 Barry Lind 提交于
-
由 Barry Lind 提交于
Fixed NPE when database name was not passed on the jdbc connection URL Fixed Connection.isClosed() to not hit the DB for every call
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 D'Arcy J.M. Cain 提交于
- Use PyObject_Del() rather than macro version - Check version and drop back to PyMem_Del() for older systems.
-
由 Bruce Momjian 提交于
Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)
-
由 Bruce Momjian 提交于
Allow CREATE TABLE AS ... SELECT in PL/PgSQL (Tom)
-
由 Bruce Momjian 提交于
< * Automatically make a view temporary if it uses a temporary table > * Require view using temporary tables to be temporary views
-
- 25 3月, 2002 7 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
> o Fix problems with complex temporary table creation/destruction > without using PL/PgSQL EXECUTE
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Automatically make a view temporary if it uses a temporary table
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 24 3月, 2002 1 次提交
-
-
由 Tom Lane 提交于
Also, fix debug logging of parse/plan trees so that the messages actually go through elog(), not directly to stdout.
-
- 23 3月, 2002 3 次提交
-
-
由 Tom Lane 提交于
there and CREATE SCHEMA will make entries in it...
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
- 22 3月, 2002 4 次提交
-
-
由 Tom Lane 提交于
addRangeTableEntry calls. Remove relname field from RTEs, since it will no longer be a useful unique identifier of relations; we want to encourage people to rely on the relation OID instead. Further work on dumping qual expressions in EXPLAIN, too.
-
由 Tom Lane 提交于
objects to be privilege-checked. Some change in their APIs would be necessary no matter what in the schema environment, and simply getting rid of the name-based interface entirely seems like the best way.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
the parsetree representation. As yet we don't *do* anything with schema names, just drop 'em on the floor; but you can enter schema-compatible command syntax, and there's even a primitive CREATE SCHEMA command. No doc updates yet, except to note that you can now extract a field from a function-returning-row's result with (foo(...)).fieldname.
-
- 21 3月, 2002 11 次提交
-
-
由 Peter Eisentraut 提交于
Report from Ryan Murray via Debian
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Dave Cramer 提交于
these versions adhere to the backend protocol better than previous version fixes problem when an error occurs on the backend, and the connection is still used previous versions were throwing an exception half way through the protocol, leaving it indeterminate. also removes empty query code, should speed things up a bit
-
由 Dave Cramer 提交于
QueryExecutor. This includes: 1) only exit after we receive a 'Z' packet 2) append error messages to a buffer and throw the exception at the end
-
由 Dave Cramer 提交于
-
由 Dave Cramer 提交于
* Introduces a new class, StartupPacket. * Moves a lot of constants from Connection to StartupPacket. * Makes two instance variables in Connection into locals.
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
okay to omit low-order dimensions when accessing an array slice.
-
- 20 3月, 2002 3 次提交
-
-
由 D'Arcy J.M. Cain 提交于
compiled with --with-pymalloc. This change fixes that. Thanks to Dave Wallace <dwallace@udel.edu>
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
- 19 3月, 2002 3 次提交
-
-
由 Bruce Momjian 提交于
> > to perform sql command: > > update pg_amop set amopreqcheck = true where amopclaid = > > (select oid from pg_opclass where opcname = 'gist_txtidx_ops'); > > Oleg, sorry, I don't understand where this should appear. In the README > file, and if so, where? Is this something only for people upgrading > from 7.2? Sorry Bruce, I was unclear. I have attached patch to Readme.tsearch Also, It'd be worth to mention in Changes to point users of tsearch about importang upgrade notices. Oleg Bartunov
-
由 Bruce Momjian 提交于
> > to perform sql command: > > update pg_amop set amopreqcheck = true where amopclaid = > > (select oid from pg_opclass where opcname = 'gist_txtidx_ops'); > > Oleg, sorry, I don't understand where this should appear. In the README > file, and if so, where? Is this something only for people upgrading > from 7.2? Sorry Bruce, I was unclear. I have attached patch to Readme.tsearch Also, It'd be worth to mention in Changes to point users of tsearch about importang upgrade notices. Oleg Bartunov
-
由 D'Arcy J.M. Cain 提交于
-