Hi, I was testing long pathnames and ran into this failure:
$ sqlite3 /tmp/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/x.db 'create table x(int y);' Error: unable to open database "/tmp/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/x.db": unable to open database file Tested with sqlite3 3.8.7.1 and 3.8.8.1 on Linux. This is due to: /* ** Maximum supported path-length. */ #define MAX_PATHNAME 512 According to http://pubs.opengroup.org/onlinepubs/009695399/basedefs/limits.h.html PATH_MAX should be at least 256 (sqlite is still good with that), but with XSI extensions PATH_MAX should be at least 1024 (_XOPEN_PATH_MAX) and sqlite3 fails there. Would it be possible to raise that limit, or output a better error message that says why it failed to open the file? Best regards, --Edwin _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
