Re: [Cgi-session-user] errors not displaying

[Matt L. <mle...@cp...>]

The error is produced because the postgresql driver binds the data to
the query with the data type (either PG_BYTEA or PG_TEXT). Thus if you
specify ColumnType => 'binary' when it's of type text, postgresql's
going to wonder wtf we're trying to do since the driver attempts to
bind as bytea and then postgresql complain about our warped sense of
reality.

In other words:
a_session is bytea, specify ColumnType => 'binary'
a_session is text, omit ColumnType or set ColumnType => 'text'
a_session is something else, fix it =)

I believe you already know this, but I'm clarifying for the other
people who might stumble upon this thread with a similar problem.

Anyway, with regard to Mark's suggestion of a PrintError, I think that
would be a good idea. Perhaps we could also make it respect an
environmental variable for on-the-fly troubleshooting.