As far as I know you need to tell it to open a file called :memory: and in Pharo-SQLite3 you should be able to use: SQLite3Connection memory
I've never done this before in Pharo, but it's worth trying, it should be faster and easier to set up. https://www.sqlite.org/inmemorydb.html https://github.com/pharo-rdbms/Pharo-SQLite3/blob/7614fe8d0ac03fc94ed6be7e61e28d9111a5d482/doc/getting_started.md#creating-a-connection On Fri, 13 Aug 2021 at 00:26, Esteban Maringolo <emaring...@gmail.com> wrote: > After I set up the tests I knew that was possible, but never knew how > to actually do it. > > Regards! > > Esteban A. Maringolo > > On Thu, Aug 12, 2021 at 8:55 PM Julián Maestri <serp...@gmail.com> wrote: > > > > Not exactly what you are asking for, but did you consider using sqlite > in memory? > > > > On Sat, 7 Aug 2021 at 23:23, Esteban Maringolo <emaring...@gmail.com> > wrote: > >> > >> I've been doing exactly that. It is, creating a new DB file for each > >> test, and I was having the same problem as you. > >> > >> I suggested a change to the driver to cover that situation: > >> https://github.com/pharo-rdbms/Pharo-SQLite3/pull/22/files > >> > >> Try applying that change and see if that works. > >> > >> I still prefer to recreate the database, it will give you a full fresh > >> start, and if you want you can halt before the deletion of the db, to > >> analyze its internal state. > >> > >> Best regards! > >> > >> > >> Esteban A. Maringolo > >> > >> On Sat, Aug 7, 2021 at 11:13 PM <vin...@gmail.com> wrote: > >> > > >> > Hi > >> > > >> > Actually I will just do a bunch of > >> > > >> > DROP TABLE IF EXISTS > >> > > >> > instead of dropping the db altogether. > >> > > >> > Thanks, Vince >
