It contains 5 records. I have to do vacuum analyze on the table after
having issued the "CREATE INDEX" to create the index?
Please, let me know...
Regards,
Denis
At 19.03 23/08/01, Doug McNaught wrote:
>Denis Gasparin <[EMAIL PROTECTED]> writes:
>
> > Hi to all!
> > I have created a
It sure is :)
On the theoretical issue, can I use TEXT field to store binary ?
If so, what will be the case with addslashes ? will it work ?
- Original Message -
From: "Joe Conway" <[EMAIL PROTECTED]>
To: "Ben-Nes Michael" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, August 2
Hello, Tom,
nope, no windows here. The file was sent direclty from the Linux to
my mailbox, which I read on Solaris.
The only thing I can think of is the PostgreSQL versions. My collegue
is using 7.0.3, and I use 7.1.2. Comments?
Miroslav
Tom Lane wrote:
Miroslav Koncar <[EMAIL PROTECTED]>
writes
Hello all,
It is my understanding that 16 parameters are allowed in a stored
procedure. If this is correct (please advise if not):
1. What are the reasons for this limitation?
2. Are there any plans to increase this number, say to 32 parameters, and
if so, when is this change expected?
3. If th
Mike Withers wrote:
>
> My apologies if the answer(s) to my questions are obvious to others. I'm
> still quite new to Linux and PostgreSQL.
>
> I have set up a database to be used by hundreds of students. Within psql I
> set GRANT SELECT ON database TO PUBLIC on the database but have found that
>
Hi Mike
On Thu, 23 Aug 2001 09:08:39 -0600, Mike Finn wrote:
>Your routine is not working becase you have no body in your function.
Well done! It now works. I didn't need to drop the operator, since
there was nothing to drop. :-)
>
>The HACK below does work. I say HACK because
>a) this routin
Steve Wampler <[EMAIL PROTECTED]> writes:
> It seems that it might be nice to have a way to set these "environment
> variables" via entries in postgresql.conf? Not that I have a good way
> to fit it into the syntax...:
>export = "SOLISDB="
> perhaps? (Or just add a pg_ctl.conf that con
Thanks; that's just what I needed. I'm glad you mentioned needing to
double-quote the trigger names!
Just in case anyone else needs to do this before they get DROP CONSTRAINT
support, I got the trigger names with:
select tgname, tgconstrname from pg_trigger where
tgconstrname='name_of_my_fore
A 'document' may consist of several records from several tables, a
relationship the DBMS doesn't understand. It also introduces alot of
complexity. You may need a way to expire locks after a certain amount of
time, or allow some users to override other users' locks.
In a system I'm working on,
Trond Eivind Glomsrød wrote:
>
> Steve Wampler <[EMAIL PROTECTED]> writes:
>
> > It looks as though the init.d script "postgres" supplied with
> > 7.1.2 no longer propagates environment variables to pg_ctl. Was that
> > an intentional change? Or is this something no one else sees?
>
> It's an
Steve Wampler <[EMAIL PROTECTED]> writes:
> It looks as though the init.d script "postgres" supplied with
> 7.1.2 no longer propagates environment variables to pg_ctl. Was that
> an intentional change? Or is this something no one else sees?
It's an unintentional sideeffect of fixing the "I cha
En un mensaje anterior, Tom Lane escribió:
> Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> > Any idea why Views do not show up in PgAccess Views tab
> > (Postgres 7.1.2, PgAccess 0.98.7)? Any idea on how to solve it?
>
> Are you *sure* you are using the up-to-date pgaccess? I'd expect
>
Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> Any idea why Views do not show up in PgAccess Views tab
> (Postgres 7.1.2, PgAccess 0.98.7)? Any idea on how to solve it?
Are you *sure* you are using the up-to-date pgaccess? I'd expect
that misbehavior from a pre-7.1 pgaccess.
On Thu, 23 Aug 2001 [EMAIL PROTECTED] wrote:
>
>
> After I created my tables, I went back and added foreign keys to them. Now I
> need to change one of the foreign keys to 'ON DELETE CASCADE' behaviour so that
> related records are automatically deleted, rather than causing an error when a
>
Hi to all!
I have created a table using the CREATE TABLE new_table (col1,col2,col3)
AS SELECT col1,col2,col3 FROM org_table.
I create an index on this table using the statement:
CREATE UNIQUE INDEX table_idx ON new_table (col1).
Then i do a select as this:
SELECT * FROM ne
Hello,
I'm looking for the jdbc driver for the newest postgresql Database.
Cause I'm stuck while compiling it, I hope that somebody outside has a
compiled version yet.
Environment:
Sun Solaris 2.7 (should not make any differences)
Postgresql is Version 7.1.3
Java is Version 1.3.0
(The compiled
It looks as though the init.d script "postgres" supplied with
7.1.2 no longer propagates environment variables to pg_ctl. Was that
an intentional change? Or is this something no one else sees?
I put databases off on their own partition, away from /var/lib/pgsql.
In the base, all I had to do wa
Steve Wampler wrote:
>
> It looks as though the init.d script "postgres" supplied with
> 7.1.2 no longer propagates environment variables to pg_ctl. Was that
> an intentional change? Or is this something no one else sees?
>
> I put databases off on their own partition, away from /var/lib/pgsql
Looks like you already have the answer. The
error message is a dead giveaway. Some field, in this case having a null
value (represented as '\N') contains a carriage return character, like:
'\NCR'. PostgreSQL cannot make sense out of this combination, so it
returns an error. The CR contai
Oliver Elphick wrote:
> Jan Wieck wrote:
> >But the question itself tells that you're about to implement
> >a major design error in your application. Holding database
> >locks during user interaction IS A BAD THING. Never, never
> >ever do it that way. And any
> key constraint is ON DELETE NO ACTION, which confusingly
> enough aborts the transaction (it's defined that way in the
> SQL standard, don't ask me why they called it NO ACTION).
NO ACTION because it takes no action on the child record? Makes sense when
you consider that
Murray Hobbs wrote:
>
> here's my problem
>
> i have tables A, B, C, D
>
> A <- B
> A <- C <- D
>
> i want to maintain integrity so that if A is deleted from then so is
> anything referencing from B and C - no problem ON DELETE CASCADE
>
> but if there are any D's that point back to A (through com
Is there any option that one might set to have PostgreSQL emit a
NOTICE when it encounters a SELECT statement having a table not
involved in any join condition?
For example, if I do:
SELECT employees.name
FROM employees, salaries;
It would aide debugging application development a bit if there w
I prefer the way Notes (for example) handles it. All
records/documents/views are in read-only mode until the user indicates
they actually want to edit. They then exclusively lock that record for
editing, with optional timeouts (in case their workstation crashes or
whatever).
This turns out to
> >But the question itself tells that you're about to implement
> >a major design error in your application. Holding database
> >locks during user interaction IS A BAD THING. Never, never
> >ever do it that way. And anybody telling you something
> >diffe
Jan Wieck wrote:
>But the question itself tells that you're about to implement
>a major design error in your application. Holding database
>locks during user interaction IS A BAD THING. Never, never
>ever do it that way. And anybody telling you something
>
> I am having a problem "activating "my copy of mysql in Redhat .7.1
> I get the following error message
>
> Can not connect to local Mysql server through socket
> /var/lib/mysql/mysql.sock
>
> I am only running a simple computer with a router firewall.
Your problem is that you are using MySQL.
27 matches
Mail list logo
