On Mon, Jul 19, 2010 at 3:51 PM, Simon Slavin <slav...@bigfraud.org> wrote:
You know, I think that the most efficient way to do what you want will > probably to always issue the 'ATTACH' command. If EventsDB is already > attached, you should get a specific error code, which you can notice but > ignore. > So, there is foul simply trying to attach and ignoring the error if there is one? That does sound ideal. > I assume that you do have a good reason to want to keep data in the > separate EventsDB file rather than the original database file. > Yea, in resent weeks I have tried and tried to figure out a way to put all the data into one DB but it just cannot happen. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users