-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/26/2010 09:48 PM, Bill Webster wrote: > Closing file handles and statement handles is not particularly drastic. Not > to be encouraged obviously, but no worse than sudden termination of the > program or power-off.
What is it exactly that leads you to want to do this abort, not keep track of what you are using, yet not want to terminate the process? Something I see some developers do is code as though all SQLite objects are precious and go to great lengths to keep them around and reuse them. This leads to complicated code. Call close/finalize or equivalent functions the moment you are done with the item. Make new items every time (eg statements and even connections). You can do profiling later to see if being profligate even shows up in the traces before going ahead and "optimising" by keeping them around long and making the code far more complicated and prone to errors. - From your mail headers it would seem you are a Windows user. Traditionally Windows developers have considered creating more than one process, or having one process per area of work done to be too expensive, especially as Windows process creation is expensive. This leads to there being a single monolithic program will all the functionality built in, lots of threads etc. You don't have to structure things that way. Using lots of single functionality processes is fine, and a heck of a lot easier to test, develop, distribute etc. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwm2uAACgkQmOOfHg372QTOkwCgqXjVgPFdMUX+8ZLE5hc8yI3N MtsAnR0Mczu5KCcL1nCC8Cw1VvPJjk6d =Mgce -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
