rly as big of a performance gain by splitting
your index up.
Take a look at partial indexes (with the WHERE clause).
http://www.postgresql.org/docs/view.php?version=7.3&idoc=1&file=sql-createindex.html
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signatu
> Hi Karim,
>
> Currently there is no way to do this other than enter the SQL yourself
> with a 'LIMIT nnn' on the end of the query. It might be handy though, so
> I'll add it to the todo list.
MSAccess does this decently. They use a cursor, pull out 100 entries by
default, then when you scrol
This would cost an extra query for every query, but you could let the DB
manage it with:
select quote_ident('user');
Just pile on all of the identifiers into a list and use the results for
the real query. This way it'll work across all versions of Postgresql
as well as future ones without any
Thats fair. The ability to rollback most changes isn't overly useful.
What is useful is the ability to replay commands on another database.
I suggest a good replacement would be a simple 'log' mode which writes
text based queries to a log file. PGAdmin should be able to play an
arbitrary text f
to confirm it can be
applied after editing.
As a side note, I still need to be able to cut & paste the SQL
generated for the purposes of a change control report.
Currently this can almost be done with the logging when you grep out
all of the selects (99.9% of the time it's pgAdmin doing it&
When clicking on a table with a comment (definition pane shows how to
create the item), data within ' ' will be highlighted as well if it
matches (see below). The word 'by' will be green.
COMMENT ON TABLE "action" IS 'Actions in queue to be services by th
