-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lukas Gebauer wrote: > You must be very unhappy about current existence of > sqlite3_get_autocommit function, right? You said, by the way: "It is > not needed, if you organize your code well." :D It is the same case!
Personally I don't use it since error conditions are handled by exceptions (the benefit of not using C :-) > Question is: > Users can ask SQLite for transaction state. But they cannot ask for > transaction name? First is useful and many users needs it, and second > not? I am surprised. It is transaction names and they are both a list and a tree. And no existing code produces a tree-list of the names, and you are the only one to ever ask for them. > But never mind, I register your response "no"! Forget it, sorry for > my bothering. I am not a member of the project nor do I speak on its behalf. I am merely trying to help you understand what happens with requests in open source projects and SQLite in particular based on several years of history. You can file a feature request at http://www.sqlite.org/src/tktnew but it will be very low priority, especially since utility to other developers has not been demonstrated. At no point have you been prevented from writing your own routine. If you want other people to do the work then you need to convince them. And for the record I did provide you with a function that would provide the information in a debugging context. You could even translate the code into something a capable debugger like gdb could use. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkq4j7QACgkQmOOfHg372QSR6QCfa2GwUyYzYh5npjqhOmNF5gE3 4Q8An2pZDrDNPrnortRAfzOagIl3JWez =rdE9 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
