Before we engage in beloved database flame wars which always produce some
enlightning thoughts, let's just say it's very frustrating to port an
application from one database to another, even in environments which promise
to abstract the underlying database, such as Java frameworks.
Check this link, it might help you:
http://www-128.ibm.com/developerworks/db2/library/long/dm-0608marino/
"internetuser" <yoapplesucks@yahoo.com> wrote in message
news:1159291505.801209.128920@d34g2000cwd.googlegroups.com...
> Ugh. How awkward. OK, thanks for the tips. I'm running into some issues
> though (see below), which make things seem pretty bizarre to me.
...
> If you can't do something this basic because of a serial column, it's
> rather lame and useless. It seems like Informix is going out of its way
> to make me write multiple statements or use temp tables to avoid doing
> things all at once like I've been doing with Oracle.
...
> Well, it's more than just annoying. It makes the statements longer,
> harder to read, and gives me twice as much to maintain, for no good
> reason as far as I can tell. Is there really no better way?
...
> There also seems to be some rather severe limitations here. Consider
> the following code that works great with Oracle:
...
> Maybe I can get the database re-designed to avoid the use of serials.
> Unfortunately, since the people who implement the database don't have
> to write the code to use it, there is probably little chance of that
> happening. These are the same people who decided to switch the
> database from Oracle 10g to Informix 9 (v.9.4.0.UC3, zero chance of
> getting a more recent version, ever) in the middle of my project, after
> a lot of database code had already been written. I'm now in the process
> of taking what was perfectly working code and make it work with
> Informix. There seems to be a number of severe limitations and lack of
> features that require one to have a very different mindset when writing
> code for Informix. Can anyone shed some light?