Robert Creager <[EMAIL PROTECTED]> writes:
> I believe OPAQUE is deprecated, and the return type of TRIGGER should be used.
Correct.
> But, I still have a trigger which I have not updated that is OPAQUE, and it
> loads just find after emitting:
> psql:dbTriggers.sql:33: WARNING: changing retu
Dear All,
I have a text file with data like:
1 2 3
4 5 6
7 8 9
i.e. so I have three columns of numbers.
I wish to put this data into a table. However, I do not want it to take up
three rows, rather only a single row and a single column. I was think
something like this
CREATE TABLE t1(data numer
Fischer Ulrich <[EMAIL PROTECTED]> writes:
> I have a problem with the restoring of a database which uses tsearch2. I
> made a backup as discribed in 'tsearch-v2-intro' on the tsearch2 page.
> Now i'm trying to restore it into a testdatabase. The problem is, that
> the entries of the relations '
Joe Lester wrote:
I'm using PostgreSQL 7.4.1. I have 140 clients connected on average
using libpq. When one client sends "NOTIFY timeclock;" to the server
all 140 clients are listening for it.
After receiving a notification from libpq (PQnotifies), each client
proceeds to execute a query for
Ben <[EMAIL PROTECTED]> writes:
> Okay, so I was actually able to answer this question on my own, in a
> manner of speaking. It seems the way to do this is to merely return a
> larger char** array, with one element for each word. But I was having
> trouble with postgres crashing, because (I think)
Hi
I have a problem with the restoring of a database which uses tsearch2. I
made a backup as discribed in 'tsearch-v2-intro' on the tsearch2 page.
Now i'm trying to restore it into a testdatabase. The problem is, that
the entries of the relations 'pg_ts_cfg', 'pg_ts_cfgmap', 'pg_ts_dict'
and '
Ashish Mahabal wrote:
Hello Hiroshi,
When I try to use the column name xmin in one of my tables I get
ERROR: column name "xmin" conflicts with a system column name
You seem to have been affected by these errors in the past too. Had you
found a solution?
Anybody else have any solutions?
The on
When grilled further on (Mon, 16 Feb 2004 07:39:25 -0500),
Terry Lee Tucker <[EMAIL PROTECTED]> confessed:
> as in, \i cust/cust_preupd_func.plsql, I get an error. The error is:
> psql:logs/logs_preupd_func.plsql:132: ERROR: ProcedureCreate: cannot change
> return type of existing function.
>
I have just upgraded Postgres from version:
PostgreSQL 7.2.3-RH on i686-pc-linux-gnu, compiled by GCC 2.96
to:
PostgreSQL 7.3.4 on i386-redhat-linux-gnu, compiled by GCC
i386-redhat-linux-gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
All of my trigger code loaded successfully; however, I am n
From http://www.sai.msu.su/~megera/oddmuse/index.cgi/Tsearch_V2_in_Brief
Table for storing dictionaries. Dict_init field store Oid of function
that initialize dictionary. Dict_init has one option: text value from
dict_initoption and should return internal representation (st
make 'SQLConnection1' Active to 'True' I get this message:
dbExpress Error: Invalid Username/Password
Maybe I need another libpq?
In SQLConnection1.params, do you have
User_name=
Password=
where is a valid postgres username
and is the correct password for that user?
kl
11 matches
Mail list logo
