Hi Steve,

I am feeling a bit uncomfortable introducing another parameter. IMHO, if this new parameter for a default null value
would be the empty string "" (not null), this would also for other non-Oracle database. We just act as Oracle and treat
empty strings like null.

In this way, we could use the empty string always and remove the externally settable parameter. This would keep the
interface simple.

Cheers, Jörg

Unfortunately, I didn't receive a notification about this comment so I just now saw it. I'm not sure I understand what you are suggesting. The issue is that the parameter cannot be null since the columns are part of the primary key. That's why the SessionID object uses empty strings as a default value. The problem is that Oracle has a vendor-specific behavior that treats empty strings as SQL NULLS. Since this is not allowed, some other value (other than an empty string) must be provided to Oracle. The purpose of the configurable parameter is to let the user choose what that special value will be.