In a specific case, we have to use such a scenario. I'm aware it is contrary to traditional way, but for this specific "mounted drive" situation, is there a reasonable solution? Any way to avoid this kind of database file corruption?
Thanks in advance, Best Regards, On Tue, Dec 24, 2019 at 12:45 PM Darren Duncan <dar...@darrenduncan.net> wrote: > On 2019-12-22 10:48 p.m., Keith Medcalf wrote: > > On Sunday, 22 December, 2019 23:20, Aydin Ozgur Yagmur < > ayagmu...@gmail.com> wrote: > >> I have experienced a weird problem. I have been using sqlite database in > >> linux by mounting. > > > > Can you give some clues what "using sqlite database in linux by > mounting" means? > > My first thought on reading that was that "mounting" meant using the > ATTACH > command, since in the analogy of the SQL environment as a filesystem, > using > ATTACH is like mounting a volume within the filesystem in order to access > the > volume's contents, which are tables. -- Darren Duncan > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
