On Thu, 05 Apr 2001 09:25:28 -0500
"Paul A. Lender" <[EMAIL PROTECTED]> wrote:
> MY QUESTION -- When query results are sent to the client, where does the
> conversion of stored binary data to easily readable text take
> place: on the server before it leaves for the clients, or at libpq.dll
> ON
Hi folks
If I want to experiment with SSL, it sounds like I need the 7.1
beta. Where do I get it?
-- Paul Lender
Paul A. Lender
University of Minnesota Department of Orthopaedic Surgery
420 Delaware St. S.E., MMC 492 Mayo
Minneapolis MN 55455
Voice: (
Uros Gruber wrote:
>Hi!
>
>I have some stupid problem wich is driving me nuts.
>
>This is my 2 tables.
>
>CREATE TABLE one ( one_id varchar(23)
> day varchar(10),
> view int4,
> two_id varchar(32),
> PRIMARY KEY (one_id)
>);
>
>CREATE TABLE two ( tow_id varchar(
Joseph writes:
> What is the difference between the Snapshot.base.tar.gz vs Snapshot.tar.gz
> in the dev folder?
>
> I regularly get one or the other and just wondered how often I should get
> the BIG one.
ftp://ftp.postgresql.org/pub/README.dist-split
--
Peter Eisentraut [EMAIL PROTECTED
"Paul A. Lender" wrote:
>
> Hi folks
>
> I submitted this directly to the novice and general news groups -- getting
> no responses -- before I had subscribed to the list, and I apologize to
> anyone who may have responded previously.
>
> I've got a FreeBSD 4.2 box running PostgreSQL 7.0.3 and W
"Oliver Elphick" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
"Tamsin" <[EMAIL PROTECTED]> writes:
> test=# delete from order_head where order_head_id = 1581;
> ERROR: overflow on numeric ABS(value) >= 10^9 for field with precision 8
> scale 2
This is extremely bizarre. A DELETE
ftp.postgresql.org:/pub/dev ...
On Thu, 5 Apr 2001, Paul A. Lender wrote:
> Hi folks
>
> If I want to experiment with SSL, it sounds like I need the 7.1
> beta. Where do I get it?
>
> -- Paul Lender
>
> Paul A. Lender
> University of Minnesota Departme
doh! now i feel _really_ stupid!
of course, I managed to forget all about the rule i made which inserts into
another table when a row is deleted. altered that table & recreated the
rule, and all is fine.
thanks tom!
tamsin
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL P
From: "Paul A. Lender" <[EMAIL PROTECTED]>
> Hi folks
>
> I've got a FreeBSD 4.2 box running PostgreSQL 7.0.3 and Windows clients
> that talk to it via LIBPQ.DLL (Zeos controls, ODBC, pgAccess...).
>
> I have a firewall on the BSD box using ipf, but I have to assume -- at
> least for the sake of
Maybe this isn't technically a bug, but I found it strange. With PostgreSQL
7.0.3 and 7.1beta6, I can create a database "FOO", but can only later connect to
it as "foo". I'm not sure if this is a psql thing or a backend thing, or if
it's intended to be this way, but it makes some of my scripts
I just ran into that too, and find it most undesirable. I don't know
whether that is part of the SQL spec or not, but it seems very odd. The
queries seem to be converted to lowercase before they ever reach the SQL
engine.
Brian
+
Flash web sites from $149/year w/ hos
On Thu, 5 Apr 2001, Brian T. Allen wrote:
> I just ran into that too, and find it most undesirable. I don't know
> whether that is part of the SQL spec or not, but it seems very odd. The
> queries seem to be converted to lowercase before they ever reach the SQL
> engine.
Everything is postgres
I'm not sure about database names but table and field names can be upper
case (or contain upper case characters) you just have to reference the
table/field in double quotes..
Example :
SELECT * FROM "FoBaR";
Hope that helps.
-Mitch
Software development :
You can have it cheap, fast or working.
I am sure it is a Good Thing, thank you for the explanation. I will just
have to change my thinking to all lowercase and get used to it.
Sort of on the same topic, does anyone know of a PostgreSQL primer for those
making the change from MySQL. Changing religions :} is never easy,
something to
Brian T. Allen wrote:
> I just ran into that too, and find it most undesirable. I don't know
> whether that is part of the SQL spec or not, but it seems very odd. The
> queries seem to be converted to lowercase before they ever reach the SQL
> engine.
Correct me if I'm wrong, but doesn
On Thu, 5 Apr 2001, Brian T. Allen wrote:
> I am sure it is a Good Thing, thank you for the explanation. I will just
> have to change my thinking to all lowercase and get used to it.
>
> Sort of on the same topic, does anyone know of a PostgreSQL primer for those
> making the change from MySQL.
Hello!
I'm working with Posgresql 7.0.3 on Red Hat linux 6.2. When I make the
following query "select * from mytable" (200 rows), I get the message:
"Backend sent D message whitout prior T" or
"Backend sent B message whitout prior T"
What is the problem?
Plese help me
Thanks
_
On Thu, 5 Apr 2001, ADBAAMD wrote:
> Brian T. Allen wrote:
>
> > I just ran into that too, and find it most undesirable. I don't know
> > whether that is part of the SQL spec or not, but it seems very odd. The
> > queries seem to be converted to lowercase before they ever reach the SQL
> > eng
Hello,
We are running Postgres 7.0.2 on Linux RH 6.2 Dell servers.
When traffic gets heavy we often get one of the backend locked up in an
UPDATE, INSERT or COMMIT request. Eventually all the other backends end
up locking too as they try to access a row locked by the original
backend. The out
ADBAAMD writes:
> Brian T. Allen wrote:
>
> > I just ran into that too, and find it most undesirable. I don't know
> > whether that is part of the SQL spec or not, but it seems very odd. The
> > queries seem to be converted to lowercase before they ever reach the SQL
> > engine.
>
> Corre
Maurice Balick <[EMAIL PROTECTED]> writes:
> Hello,
>
> We are running Postgres 7.0.2 on Linux RH 6.2 Dell servers.
As I understand it, 7.0.3 fixes some severe bugs in earlier 7.0
versions. You should upgrade to 7.0.3 at the very least, and consider
upgrading to 7.1, which is currently in Rel
"Hector Miranda" <[EMAIL PROTECTED]> writes:
> I'm working with Posgresql 7.0.3 on Red Hat linux 6.2. When I make the
> following query "select * from mytable" (200 rows),
You're running out of application memory for the query result. (libpq
doesn't recover from that too gracefully, unfortu
Peter Eisentraut wrote:
> ADBAAMD writes:
>
>> Brian T. Allen wrote:
>>
>>> I just ran into that too, and find it most undesirable. I don't know
>>> whether that is part of the SQL spec or not, but it seems very odd. The
>>> queries seem to be converted to lowercase before they ever reach the
23 matches
Mail list logo
