Re: Difficulty inserting a large object using DBD::Pg

I found this when reading the documentation on the PostgreSQL site:
A column of type OID is similar to an INTEGER column, but defining it as type OID documents that the column holds OID values.

The second snippet you showed using "do" works when $value is an integer. Also since, "atoi error" points to a problem while converting ASCII to integer, I think the evidence points to OIDs being integer-only.

Comment on Re: Difficulty inserting a large object using DBD::Pg

Replies are listed 'Best First'.
RE: Re: Difficulty inserting a large object using DBD::Pg (kudra: int->OID possible, but doesn't fix ) by kudra (Vicar) on Jun 29, 2000 at 19:22 UTC
I'm not sure what you're suggesting. Is it: `my $value = "111"; $dbh->do("insert into foo(id, test) values (8, ?)", undef, $value);` [download] Certainly that will allow an insert, but then 111 becomes the value of the column, not an OID. Exporting it therefore doesn't work: `foobar=> select lo_export('test', '/tmp/x') from foo where id=8; ERROR: pg_atoi: error in "test": can't parse "test"` [download] If the OID is a valid number, I imagine it will work, but then I still have to insert the data and get an OID, which puts me back to using lo_import. Or did I misunderstand your suggestion?	[reply] [d/l] [select]

Replies are listed 'Best First'.

RE: Re: Difficulty inserting a large object using DBD::Pg (kudra: int->OID possible, but doesn't fix )
by kudra (Vicar) on Jun 29, 2000 at 19:22 UTC

my $value = "111";
$dbh->do("insert into foo(id, test) values (8, ?)", undef, $value);
[download]

foobar=> select lo_export('test', '/tmp/x') from foo where id=8;
ERROR:  pg_atoi: error in "test": can't parse "test"
[download]

[reply]
[d/l]
[select]