Re: Boolean casting in 7.3 -> changed?

> I didn't see an answer to this question, but I sincerely hope that the
> answer is
> "no." Otherwise, dynamic interfaces are going to have a much harder
> time.
>
> Take DBI (and DBD::Pg), for example. Most DBI users don't specify a
> data type when using placeholders. Therefore, DBD::Pg (and other DBDs,
> including DBD::Oracle) assume that the data types are strings. So it's
> not unusual for DBD::Pg to execute a query like this:
>
>    INSERT INTO foo (numtype, varchartype, datetime, inttype)
>         VALUES ('23.4', 'string', '2002-11-30 00:00:00', '12');
>
> In order to allow the flexibility to remain, AFAICT PostgreSQL has to
> continue to allow strings to be converted to numbers on the back end.

I have to agree with david on this one.  It's essential that quoted numbers
be allowed into number fields.  I have no problem with putting numbers in
boolean fields though.

Chris