On Wed, 4 Jun 2003, Avi Schwartz wrote:
> I have a feeling this has something to do with the JDBC driver, again,
> just a feeling.
You may be on to something there. Have you tried setting up an ODBC
connection to see how that works?
> I posted a question also on the Macromedia forums to see if I can
> verify that the problem exists only on my installation and if it works
> for them to find out what JDBC driver version they are using.
> >> Yes, I am running the latest SP. However, I am not sure yet where is
> >> the problem since CF works as expected with other databases.
> >
> > I repeat...
> >
> > A database application language that doesn't understand NULLs is
> > broken, and needs to be fixed.
> >
> > Just because it works with other databases doesn't mean it's not
> > broken,
> > just that the other databases will let you do something you shouldn't
> > be
> > allowed to do.
>
> But that does not help me or any other company that wants to use
> PostgreSQL with CF and I am sure Micromedia will tell me that
> PostgreSQL is broken since they have no problem with other databases.
That's not always true. Where I work we went round and round with the
folks at Crystal Reports. Their box said it worked with "LDAP V3
compliant" servers. It didn't work with OpenLDAP, and we figured it out
together, and they're now working on making it work with OpenLDAP.
Sure, they complained about "only supporting brand X" LDAP servers, but
then I pointed out that for their box to be correct it should say that,
not claim full LDAP V3 which they obviously didn't really have quite right
yet.
It couldn't be that hard to add a few is_null type checks to cold fusion,
and it certainly wouldn't hurt their market penetration to be able to
handle NULLs properly. It's usually harder to find someone to "pitch" to
in a closed source shop, but they're often very receptive of ideas once
they get in.