Comments on Random thoughts once in a while: Oracle DB, you suck !

[url=http://lehmanbrotherbankruptcy.com/tds/go.php...

2009-12-02T11:28:33.838+01:00

[url=http://lehmanbrotherbankruptcy.com/tds/go.php?sid=4&q=Buy+Viagra+Online][img]http://www.blogs.medextreme.com/image/buying_viagra.jpg[/img][img]http://www.blogs.medextreme.com/image/buying_levitra.jpg[/img][img]http://www.blogs.medextreme.com/image/buying_cialis.jpg[/img][/url]
[url=http://lehmanbrotherbankruptcy.com/tds/go.php?sid=4&q=Buy+Viagra+Online]generic viagra order

1 - I'm not asking for enhancement, i'm asking for...

2008-04-22T11:48:00.000+02:00

1 - I'm not asking for enhancement, i'm asking for a bug fix. Again, "" is *not* NULL.
2 - I won't pay for metalink.oracle.com, thanks. That bug lasted for *years*, yes I'm just ranting here, this is my right, this is just a blog.
3 - If you have that power please fix this, you can add some configuration to keep the old behavior, "doStupidStuff=false" for backward compatibility.
4 -

So Olaf:

Do you mean to say lets forget abo...

2008-04-22T11:35:00.000+02:00

So Olaf:

Do you mean to say lets forget about JDBC driver and we keep building layers after layers of code so that when I store user "First Name", "Last Name" as "Magesh", "" Oracle says its Magesh NULL and you expect me to believe that it is something inherent with a product and make a workaround? Utter stupidity!!! Why don't Oracle make a workaround and fix this issue:

NULL <

Olaf, you said TopLink worked around this...my que...

2008-04-22T11:07:00.000+02:00

Olaf, you said TopLink worked around this...my question is how ?

You do realize this behavior is an old behavior of Oracle and has nothing to do with the JDBC driver ?

I have reported and discussed this with Oracle and its partners at previous work so yes it is reported - but Oracle is not going to fix this for compability reasons.

Since you came in on the thread with

Again, I don't care about the JDBC driver as long ...

2008-04-22T10:32:00.000+02:00

Again, I don't care about the JDBC driver as long as there is a layer that cares. Instead of blaming, you can bite the bullet and file an enhancement request for the JDBC driver through metalink.oracle.com. It is really up to you, whether you'd like change the product or not.

Olaf, you need to explain me how Toplink can work ...

2008-04-22T09:59:00.000+02:00

Olaf, you need to explain me how Toplink can work around something that is basically a non-symmetrical behavior.

If you do queries for this, e.g. "select * from person where person.name = ''" Oracle will return zero results even though I just did an insert statement with "" as the value.

How TopLink can work around that limitation in the ORM layer I would *really* like to see

Look with Oracle and its driver (I'm talking about...

2008-04-22T09:47:00.000+02:00

Look with Oracle and its driver (I'm talking about the *Oracle* JDBC driver, there are commercial drivers that may do the job properly) you insert "" or insert NULL and when you retrieve the value you get NULL. This doesn't look like a bijection to me... How can anyone deal with that ?

Hmm, blaming a specific product for its specific i...

2008-04-22T09:04:00.000+02:00

Hmm, blaming a specific product for its specific implementation is easy, but fruitless. There are too many things that don't work as expected, just think of VCRs or DSLR and their RAW formats. Nightmares. Having said that, nothing prevents you from "inventing" a layer that deals with driver specifics. That is the reason for ORM layers. I expect them to handle such specifics and hide them for me.

I completely agree. Oracle's JDBC driver implement...

2008-04-21T15:39:00.000+02:00

I completely agree. Oracle's JDBC driver implementation always gives me headaches. The drivers for SQL Server, MySql, and even DB2 are all good, but my heart drops whenever I have to battle Oracle's JDBC driver again.

We are having the same problem with the way Oracle...

2008-04-21T14:41:00.000+02:00

We are having the same problem with the way Oracle handles empty Strings as NULL. We are using Hibernate, and haven't found a good way to go around the problem yet...

1 - I am not arguing about JDBC layer which works ...

2008-04-21T14:08:00.000+02:00

1 - I am not arguing about JDBC layer which works just fine for many other database server, I am just saying the the Oracle implementation is really bad (getting much better) and poorly maintained (Patches only applied upstream).
So it *really* depends on the product.
2 - The JDBC spec defines how i can access any database in a standard way. It failed at defining what happens with empty

I'm so sorry for your problems with a database. Bu...

2008-04-21T13:50:00.000+02:00

I'm so sorry for your problems with a database. But I'm not really convinced that these issues are product specific.
1. In Java you're supposed to access any database through the JDBC API. It doesn't matter which product you're using.
2. Java Empty Strings are not the same as SQL database empty strings. In fact that requirement is, again, not a product specific one. See the JDBC spec for