-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/21/2010 04:47 AM, Igor Sereda quoted Oracle: >> The application-level behavior of the two products is identical,
I did test the Oracle version a few months ago and found that statement to be false. Oracle know about the issues but gave the impression that they would not be fixing a SQLITE_BUSY related one (the entire process hangs instead of busy error being returned) claiming performance benefits! Random examples of other things that broke and might eventually be fixed: - - :memory: databases have an arbitrary (small) limit on size - - VFS calls/usage are ignored without error - - Backup not implemented but returns ok - - Different error codes and behaviour when database is corrupt or not a database - - Files can be re-opened by name during the lifetime of a connection, which allows for various attacks/permissions issues. (By contrast SQLite opens the file once during sqlite3_open so deleting/renaming/permissions does not cause later errors.) - - There is no easy equivalent to the amalgamation (there is an amalgamation but it doesn't compile) On the SQL side I didn't detect any difference. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwflTYACgkQmOOfHg372QTY0gCeNIw3nhVM+Bq1lJ2VLE+tJE5A MS4AnitLodGhk5O44KIx3PFLsmmbMUhs =gM74 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
