Hello Scott,
PostgreSQL also supports regular expressions, _VERY_ useful..;-)
~* regular expression, case-insensitive..;-)
Try to get a copy of Bruce's book
Introduction and Concepts
by Bruce Momjian
A sample from the book:
SELECT * FROM friend WHERE firstname ~* '[bc]'
read it online,
We intend to move from M$ Access to PostgreSQL, however, much of our legacy
code operates under the assumption that string or text comparisons are case
insensitive whereas postgres is case sensitive. This issue extends to SQL
Select statements as well as straight comparison (i.e. in addition to t
Another method is to create a new table with only the desired fields with
the SELECT INTO query
i.e. SELECT INTO TABLE FROM
then, after deleting the old table, you will need to rename the new,
temporary table, to that of your old table. Your conditions will need to
be reset with the new t
On Mon, 13 Aug 2001 17:30:50 GMT, Jova <[EMAIL PROTECTED]> wrote:
> how do spool my results to a file.
> I know there is a command spool on and off. How do I use it?
>
\o
then
\o
to shut it off
looks like
\g
does something similar for single queries (I did not know that).
remember \? too
I wrote:
> 3. As a separate proposal, we could change COUNT()'s running counter
> and output datatype from INT4 to INT8. This would make it a little
> slower but effectively overflow-proof.
> * Changing the output datatype of these operations --- especially COUNT
> --- might affect or even break
Allan Engelhardt <[EMAIL PROTECTED]> writes:
> 1. Should I worry about these messages at all?
No.
> 2. Is it supported to VACUUM a database with open transactions?
Yes.
regards, tom lane
---(end of broadcast)---
TIP 5: Ha
