On Mon, 23 Apr 2001 16:30:43 -0400, Fran Fabrizio alluded:
>
> Hello,
>
> It seems that there should be a way to install the DBD Pg module without
> having to install postgres on the local machine. I tried installing
> just the libs rpm, but that didn't seem to do the trick. I've done s
On Mon, 23 Apr 2001, Paul Tomblin wrote:
> Is the "BETWEEN" clause inclusive or exclusive? ie if I say "WHERE
> latitude BETWEEN 45 and 55", will I get examples where the latitude equals
> 45 or not? Also, is "latitude BETWEEN 45 and 55" any more efficient than
> "latitude >= 45 AND latitude <=
Is the "BETWEEN" clause inclusive or exclusive? ie if I say "WHERE
latitude BETWEEN 45 and 55", will I get examples where the latitude equals
45 or not? Also, is "latitude BETWEEN 45 and 55" any more efficient than
"latitude >= 45 AND latitude <= 55", or is it just a stylistic thing?
--
Paul T
I recently upgraded my production server
to 7.1 because people keep saying how
performance is so much better than 7.0.3
and because 8k row length limitation was removed
postgres is accessed by mod_perl processes
maintaining persistent connections. Before
I can count the number of mod_perl proce
on 4/23/01 9:20 PM, Randall Perry at [EMAIL PROTECTED] wrote:
> This works:
> $res = $conn->exec("select cust, contact, user_name, email from $t where
> user_name = a1a");
>
> This doesn't:
> $c = "a1a";
> $res = $conn->exec("select cust, contact, user_name, email from $t where
> user_name = $
At 04:30 PM 23-04-2001 -0400, Fran Fabrizio wrote:
>
>Hello,
>
>It seems that there should be a way to install the DBD Pg module without
>having to install postgres on the local machine. I tried installing
>just the libs rpm, but that didn't seem to do the trick. I've done some
>usenet and maili
This works:
$res = $conn->exec("select cust, contact, user_name, email from $t where
user_name = a1a");
This doesn't:
$c = "a1a";
$res = $conn->exec("select cust, contact, user_name, email from $t where
user_name = $c");
and returns the error:
Attribute 'a1a' not found
How do you
On Tue, 24 Apr 2001, Thomas Lockhart wrote:
> > > ... if there is interest in an A4 layout of the docs, let me know...
> > I've gotten several requests for the A4 format, and have completed four
> > of the six docs in that format. Thanks for the feedback. They should be
> > available in the next
> > ... if there is interest in an A4 layout of the docs, let me know...
> I've gotten several requests for the A4 format, and have completed four
> of the six docs in that format. Thanks for the feedback. They should be
> available in the next couple of days...
OK, A4 docs are now posted on the
Limin Liu <[EMAIL PROTECTED]> writes:
> + NOTICE: _outNode: don't know how to print type 726
> + NOTICE: _outNode: don't know how to print type 726
This is pretty harmless, but if you don't want to see it, don't
start your postmaster with -d above 2.
Someday, someone ought to add FkConstraint
> I don't know a lot of detail about how DBD::Pg works, but I do know that
> during installation (whether from tarball or CPAN, which I think is the
> best way to install perl modules), it requires the path of your postgres
> libraries and includes - so I guess it depends on a postgres
> installat
On Monday 23 April 2001 06:04 pm, Lamar Owen wrote:
> Fran Fabrizio wrote:
> > Hello,
> >
> > It seems that there should be a way to install the DBD Pg module without
> > having to install postgres on the local machine. I tried installing
> > just the libs rpm, but that didn't seem to do the tric
I perform a complex select-operation on a database with 10.000 entries
and with various Where-clauses I get 200 results. Now I want to get
the position of one special entry (identified by its OID) in this
selection.
Background: The user can fully customize a query in an online-database
(sort by,
Jeff Eckermann <[EMAIL PROTECTED]> writes:
> I am attempting to do a pg_dump, preparing to upgrade to 7.1.
> I have attempted a pg_dumpall, as well as pg_dump for various individual
> databases, and each fails with the message "dumpProcLangs(): handler
> procedure for language plpgsql not found"
> What's the dependencies for the DBD::Pg RPM? Satisfy those
> dependencies, and properly set up for client-server communications with
> a postgresql server, and it _should_ just _work_.
Well, if I had known what it took to satisfy the dependencies, I wouldn't
have needed to post here. ;-)
Hello all,
Any ideas how I can duplicate the auto increment feature that MySQL uses in
PostgreSQL? (Other than doing a query to find the next number in que)
Just thought I'd ask.
Thanks,
Kevin
_
Get your FREE download of MSN Expl
That fixed it! Thanks!
Hunter
> From: Stephan Szabo <[EMAIL PROTECTED]>
> Date: Mon, 23 Apr 2001 14:54:50 -0700 (PDT)
> To: Hunter Hillegas <[EMAIL PROTECTED]>
> Cc: PostgreSQL <[EMAIL PROTECTED]>
> Subject: Re: [GENERAL] Query Question
>
> On Mon, 23 Apr 2001, Hunter Hillegas wrote:
>
>> I ha
Fran Fabrizio wrote:
>
> Hello,
>
> It seems that there should be a way to install the DBD Pg module without
> having to install postgres on the local machine. I tried installing
> just the libs rpm, but that didn't seem to do the trick. I've done some
What's the dependencies for the DBD::Pg
On Mon, 23 Apr 2001, Hunter Hillegas wrote:
> I have 4 tables: releases, artist_info, categories, and formats.
>
> I am using this query:
>
> SELECT DISTINCT *, categories.category_name as category_name,
> categories.rec_num as category, formats.format_name as format_text,
> releases.rec_num as
Hello,
It seems that there should be a way to install the DBD Pg module without
having to install postgres on the local machine. I tried installing
just the libs rpm, but that didn't seem to do the trick. I've done some
usenet and mailing list archive searches, but all the info I'm turning
up
I have 4 tables: releases, artist_info, categories, and formats.
I am using this query:
SELECT DISTINCT *, categories.category_name as category_name,
categories.rec_num as category, formats.format_name as format_text,
releases.rec_num as release_rec_num, artist_info.name as artist_name FROM
rele
21 matches
Mail list logo