The thing is...I am not. I am inserting it into a varchar field.
$sql=insert into it_contact (email, to_email, subject,
details,modify,parent) values(?,?,?,'$body',now(),'$parent');
$sth = $dbh-prepare($sql);
$sth-bind_param(1, $from, {pg_type = DBD::Pg::PG_TEXT});
I have to convert an java web application currently using an Oracle DB
back end to one using a Postgres backend.
In Oracle much of the application logic is abstracted away from the java
middleware layer using stored procedures within the Oracle database. There
are certain features in Oracle that
On Wed, 2003-12-03 at 07:02, David Garamond wrote:
What do people recommend for storing money amounts? I've seen people use
NUMERIC(18,3) and other use NUMERIC(18,4). Which one is more appropriate
and why? This is considering various existing currencies, some having
low rates (like IDR, in
Oliver Elphick wrote:
You should not regard amounts in different currencies as equivalent.
You cannot add Euros to dollars and get a meaningful figure; so they
should not be in the same column.
I plan to store amount in a column (NUMERIC) and currency id in another
(CHAR(3)). Plus another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I want to change a column from text to bytea; since it seems that alter
table can't change the column type, i have to add a temporary column and
copy the data from the old one to the new, delete the old and rename the
new.
But it seems that
On Wednesday 03 December 2003 08:08, John Sidney-Woollett wrote:
I have to convert an java web application currently using an Oracle DB
back end to one using a Postgres backend.
[snip]
Issue - nested transactions
=
[snip]
This is an issue for us because some procedures make use of a
Ausrack Webmaster wrote:
The thing is...I am not. I am inserting it into a varchar field.
Are there any single quotes in the message body? They will wreak havoc
with the rest of the query. And why are you putting single quotes around
'$parent'?
What happens if you move the '$body' to the end:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Alvar Freude [EMAIL PROTECTED] wrote:
But it seems that Postgres can't cast text to bytea:
odem= UPDATE forum_gtree SET gid2=gid::bytea;
ERROR: Cannot cast type text to bytea
I tryed it with DECODE:
odem= UPDATE forum_gtree SET
Tried that ...it is definetely the to_email field, not any others that
is causing
the problem.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex Satrapa
Sent: Wednesday, December 03, 2003 6:31 PM
To: Ausrack Webmaster
Cc: [EMAIL PROTECTED]
On Wednesday 03 December 2003 09:43, Ausrack Webmaster wrote:
Tried that ...it is definetely the to_email field, not any others that
is causing
the problem.
With the table schema you gave, the following seems to work fine for me. Only
changes from your example are to remove quoting on $parent
My question is why??? The two insert operations do not
conflict with each other (at least not in the
real-world situation). Also, why does the foreign key
make a difference?
I don't know if this would help, but given the other explanations you've
gotten I would try setting the foreign key
Is there a way from C++ to essentailly use postgresql as an embedded
database? I have a situation where I'd rather have a postgrtes daemon
running on my customer's machine except when my client application is up.
Preferably I'd like to not have to establish a network connection, and
hence use the
PG only runs as a daemon. However, you can connect over UNIX-domain
sockets rather than Internet sockets if you want.
Jon
On Wed, 3 Dec 2003, Gregory Stone wrote:
Is there a way from C++ to essentailly use postgresql as an embedded
database? I have a situation where I'd rather have a
If you cannot make your transactons shorter (and
please don't tell me
that you have user interaction going on while
holding any open
transactions), then you might be able to increase
your concurrency by
deferring the foreign key check until commit.
oh! my! gawd!!!
THANK YOU!
If you cannot make your transactons shorter (and
please don't tell me
that you have user interaction going on while
holding any open
transactions), then you might be able to increase
your concurrency by
deferring the foreign key check until commit.
oh! my! gawd!!!
THANK YOU! The
Dr NoName wrote:
If you cannot make your transactons shorter (and
please don't tell me
that you have user interaction going on while
holding any open
transactions), then you might be able to increase
your concurrency by
deferring the foreign key check until commit.
oh! my! gawd!!!
THANK YOU!
Jan,
To continue the brain-dump. I was curious how the GC protocol was going to be
implemented (if you had any ideas thus far).
Several years ago, I started working on a network security and intrusion
detection system for a client where the audit/logging system needed to be
redundant- they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the following I posted already on pgsql-bugs -- perhaps someone has a good
workaround or fix or can say me that I'm wrong?
There seems to be a bug in handling bytea columns with index and the
like-operator.
When an index scan on a bytea column
CM == Carlos Moreno [EMAIL PROTECTED] writes:
CM What would be your advice? Is 7.3.4 the recommended one
CM if we need reliability? Or has 7.4 earned sufficient
CM trust by now?
CM Also, how about back compatibility? Should I expect some
CM trouble? I remember with one of the previous
Keith C. Perry wrote:
Jan,
To continue the brain-dump. I was curious how the GC protocol was going to be
implemented (if you had any ideas thus far).
The stuff I've been kicking around so far is Spread 3.17.1 with a simple
self made Tcl/Tk binding library used from inside PG via PL/TclU. You
Tom Lane wrote:
Chris Travers [EMAIL PROTECTED] writes:
Also, I am a little confused by Tom's statement that we don't have the right
to modify the license.
I don't see what's confusing about it. Our implicit contract with
contributors (past and present) is that we'd distribute their work
On Dec 3, 2003, at 1:05 PM, Vivek Khera wrote:
CM == Carlos Moreno [EMAIL PROTECTED] writes:
CM What would be your advice? Is 7.3.4 the recommended one
CM if we need reliability? Or has 7.4 earned sufficient
CM trust by now?
CM Also, how about back compatibility? Should I expect some
CM
The deferred foreign key checks are exactly
what I needed. They are quite useful for other reasons
too.
I believe Postgres is just following standards.
Yes, deferred is very useful for other things, like a real data model layer
mediating between UI and database--without it you have to worry
Hello pgsql-general,
It appears 7.4 is not published in all the usual places so I was
wondering if there's a yum repository with updated packages available
and if not then what's the approach that will cause the least amount
of pain? I do realize I'll need to dump/restore, just want some expert
Ok...this has irritated me for sometime. I've seen reference to dividing
it up into proper syllables in the mailing archives, but couldn't find
pronunciation of the gres part...
Is it:
Post - grease - queue - el
Post - greee - es - queue - el
or
Post - gress - queue - el (as in impress)
Yeah... I found a link to the sound file in a archived message, but it's
404 now...
John
Dann Corbit said:
I always say:
Pigee - squeal.
At least it's easy to remember.
None of the below exactly roll off the tongue. I seem to remember a
site that had a sound file attachment for how to
I always say:
Pigee - squeal.
At least it's easy to remember.
None of the below exactly roll off the tongue. I seem to remember a
site that had a sound file attachment for how to pronounce PostgreSQL,
but I can't remember where I saw it.
-Original Message-
From: John Wells
I use your third pronunciation
Regards,
Chris Stokes
Senior Systems Consultant
Bass Software
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Main +613 8415 9300
Direct +613 8415 9305
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of John Wells
Me too.
On Thu, 4 Dec 2003, Chris Stokes wrote:
I use your third pronunciation
Regards,
Chris Stokes
Senior Systems Consultant
Bass Software
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Main +613 8415 9300
Direct +613 8415 9305
-Original Message-
From: [EMAIL
John Wells wrote:
Ok...this has irritated me for sometime. I've seen reference to dividing
it up into proper syllables in the mailing archives, but couldn't find
pronunciation of the gres part...
FOLDOC (Free Online Dictionary of Computing) says:
PostgreSQL
database /'post-gres-kyu-el/ An
I just say postgres
Dann Corbit wrote:
I always say:
Pigee - squeal.
At least it's easy to remember.
None of the below exactly roll off the tongue. I seem to remember a
site that had a sound file attachment for how to pronounce PostgreSQL,
but I can't remember where I saw it.
Post - gress - Q - L
On Wed, 3 Dec 2003, John Wells wrote:
Ok...this has irritated me for sometime. I've seen reference to dividing
it up into proper syllables in the mailing archives, but couldn't find
pronunciation of the gres part...
Is it:
Post - grease - queue - el
Post - greee -
On Thu, 4 Dec 2003, Craig O'Shannessy wrote:
Me too.
Its the way I've always pronounced it ...
On Thu, 4 Dec 2003, Chris Stokes wrote:
I use your third pronunciation
Regards,
Chris Stokes
Senior Systems Consultant
Bass Software
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
You could do something with threads on the backend, invisible to your Java
middleware. I don't have enough experience to feel confident about trying to
evaluate the pros and cons of (possibly) different ways of doing this. But
given that you can write functions in C and load them into Postgres so
After several fixes were backpatches to the 7_3_STABLE branch, we have now
released a 7.3.5. As the list of Changes since 7.3.4 is quite small, they
are included in this email:
* Force zero_damaged_pages to be on during recovery from WAL
* Prevent some obscure cases of variable
They're used to be a sound bite on postgres.org on how to pronounce it
properly.. any idea where that went?
Travis
-Original Message-
From: Marc G. Fournier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 7:46 PM
To: Craig O'Shannessy
Cc: Chris Stokes; John Wells; [EMAIL
36 matches
Mail list logo
