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 $pare
]
Subject: Re: [GENERAL] DBD::Pg problem
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
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:
sday, December 03, 2003 3:52 PM
To: Ausrack Webmaster
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] DBD::Pg problem
pg_atoi is the string to int converter. You're trying to insert it into
an integer field.
On Wed, Dec 03, 2003 at 03:45:53PM +0900, Ausrack Webmaster wrote:
> Hi
>
> I a
pg_atoi is the string to int converter. You're trying to insert it into an
integer field.
On Wed, Dec 03, 2003 at 03:45:53PM +0900, Ausrack Webmaster wrote:
> Hi
>
> I am trying to insert a simple email address into a text field,
> and I get the below error:
>
> DBD::Pg::st execute failed: ER
Hi
I am trying to insert a simple email address into a text field,
and I get the below error:
DBD::Pg::st execute failed: ERROR: pg_atoi: error in
"<[EMAIL PROTECTED]>": can't parse "<[EMAIL PROTECTED]>"
I figure it is because of the < and @ in the value, but why does it take
these as operat
The DBD::Pg perl module for some reason has a limit of 8140 bytes when
inserting, and I don't see why (yeah, I'll be contacting the authors there
too), but I thought I'd ask here... I'm writing a Postgres-backed mail
client, and storing emails in the database is obviously a little difficult
wh