Re: DBI/DBD::Pg changing my sql query somehow?

Hmm .. I see

insert into crowdtangle (postUrl, ..

and then

DBD::Pg::st execute failed: ERROR: column "posturl" of relation ..

which leads me to believe that these fields are case-sensitive. (So, the field name should be a uniform choice of posturl, and not postUrl.)

Alex / talexb / Toronto

Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.

Comment on Re: DBI/DBD::Pg changing my sql query somehow?

Replies are listed 'Best First'.
Re^2: DBI/DBD::Pg changing my sql query somehow? by cavac (Prior) on Jul 25, 2024 at 07:17 UTC
PostgreSQL is case sensitive. But it auto-lowercases table and column names (among other identifiers) in statements, unless you enclose them in double-quotes "". In this case, this leads to a mismatch. Mostly because someone unwisely created the table with mixed-case column names. PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP Also check out my sisters artwork and my rather simple sketches/one-panel comics	[reply]
Re^3: DBI/DBD::Pg changing my sql query somehow? by parv (Parson) on Jul 25, 2024 at 08:15 UTC
Using mixed case for column names is "unwise" if they are not quoted (as mentioned at URLs linked elsewhere in this thread). OP could get on with life with quoting them (in their queries).	[reply]
Re^3: DBI/DBD::Pg changing my sql query somehow? by hippo (Archbishop) on Jul 25, 2024 at 08:43 UTC
Mostly because someone unwisely created the table with mixed-case column names. It's even worse than that. Someone created the table with column names arbitrarily scattered between camelCase and snake_case. That's just inviting doom. 🦛	[reply]