> I don't know about postgres, but it cannot be worse than Oracle.
> 4 points about difficulties:
> - Oracle datatypes, 32Kbytes field doesn't exist and more than one LONG
(4Mb)
> field by table is excluded
Same for postgres - tuple (row) size can't exceed disk segment size. Larger
fields have to go to blobs. Unfortunately blobs are not well supported.
> - mysql date function conversion
Can you elaborate?
> - auto_increment column
Postgres has SERIAL, I am sure Oracle has something like that too. It can
also be emulated with triggers.
> - number of rows after a select
Do you mean the SELECT should return the number of affected rows without
parsing of returned recordset?
Gene Sokolov.
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
