Re: OOP/OOD Philosophy

>> Anyway, I am developing applications which are vendor independent by
>> using ANSI SQL. It is possible for me.
>Sure by avoiding dates, sequences

I don't avoid dates, it is no problem. I do avoid sequences, but I am
quite sure it would be possible to do vendor independent applications
using sequences too. The syntax for createing a sequence may be
different for different vendors, but the applications does not have to
care about that. It just put null in that field and the RDBMS creates a
sequence number.

> and anything else beyond "select *
>from Blah" and basic joins.

I am working with an human resource application used by the swedish
police, military and goverment, that currently runs on both Oracle and
Informix. I can ensure you that we do more than "select * from Blah".

>All business applications I've dealt with require dates and unique
>keys.

If you really can't use dates and sequences it is not a big deal
skipping these types. Use a long or string instead of the date, and
make a helper class that converts the long value to a date. Sequences
are very easy to live without. Just make a "select max(id) from
mytable" before you do the insert.

Fredrik Bertilsson
http://butler.sourceforge.net

.