| Age | Commit message (Collapse) | Author |
|---|
|
in schemas other than the system namespace; however, there's no search
path yet, and not all operations work yet on tables outside the system
namespace.
|
|
support
|
|
Fixed NPE when database name was not passed on the jdbc connection URL
Fixed Connection.isClosed() to not hit the DB for every call
|
|
|
|
|
|
- Use PyObject_Del() rather than macro version
- Check version and drop back to PyMem_Del() for older systems.
|
|
Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)
|
|
Allow CREATE TABLE AS ... SELECT in PL/PgSQL (Tom)
|
|
< * Automatically make a view temporary if it uses a temporary table
> * Require view using temporary tables to be temporary views
|
|
|
|
> o Fix problems with complex temporary table creation/destruction
> without using PL/PgSQL EXECUTE
|
|
|
|
> * Automatically make a view temporary if it uses a temporary table
|
|
|
|
|
|
|
|
Also, fix debug logging of parse/plan trees so that the messages actually
go through elog(), not directly to stdout.
|
|
there and CREATE SCHEMA will make entries in it...
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
Report from Ryan Murray via Debian
|
|
typedefs from SQL ones.
|
|
|
|
|
|
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
|
|
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
|
|
|
|
StartupPacket
* Introduces a new class, StartupPacket.
* Moves a lot of constants from Connection to StartupPacket.
* Makes two instance variables in Connection into locals.
|
|
|
|
|
|
okay to omit low-order dimensions when accessing an array slice.
|
|
compiled with --with-pymalloc. This change fixes that. Thanks to
Dave Wallace <dwallace@udel.edu>
|
|
|
|
|
|
installing)
> > 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
|
|
installing)
> > 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
|
|
|
|
|
|
feature.
I'll do ALTER TABLE / DROP CONSTRAINT next...
Christopher Kings-Lynne
|
|
Neil Conway
|
|
|
|
> * -Add domain capability [domain] (Rod Taylor)
|
|
|
|
in the current code, the authentication logic (check user, check the
relation we're operating on, etc) is done in tcop/utility.c, whereas the
actual TRUNCATE command in done in TruncateRelation() in
commands/createinh.c (which is really just a wrapper over
heap_truncate() in catalog/heap.c). This patch moves the authentication
logic into TruncateRelation(), as well as making some minor code
cleanups.
Neil Conway
|
|
* We should not even consider checking the row if it is no longer
* valid since it was either deleted (doesn't matter) or updated
* (in which case it'll be checked with its final values).
Stephan Szabo
|
|
> Korean (JOHAB), Thai (WIN874),
> Vietnamese (TCVN), Arabic (WIN1256)
>
>Added ClientEncoding
> Simplified Chinese (GBK), Korean (UHC)
>
>Add PsqlODBC and document ...etc patch.
"JDBC patch" is delivered, too. :-)
Eiji Tokuya
|
