This is most likely done to reduce compiled code size. For a lot of systems this code probably is wasted space, as the feature is not used everywhere. For embedded systems the ability to simply cut features at compile time to reduce code size is very important.
Mike -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Nicolas Williams Gesendet: Dienstag, 19. Februar 2008 23:58 An: General Discussion of SQLite Database Betreff: [sqlite] Given sqlite3_enable_load_extension(),why omit loadable extensions? I searched and found that SQLITE_OMIT_LOAD_EXTENSION is defined by default to protect applications that might otherwise unwittingly allow SQL that loads extensions. I understand that, but, by default extensions cannot be loaded until sqlite3_enable_load_extension() is called to enable them. So why still define SQLITE_OMIT_LOAD_EXTENSION by default? Are loadable extensions an unstable part of SQLite3? Some other reason? Nico -- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
