Well then, the initial changes were pushed to my runServer branch. <br><a href="http://github.com/mlaite/pony-build/commit/c07bc5c15d5b8e3636f4c3d71258033208a5bd9e">http://github.com/mlaite/pony-build/commit/c07bc5c15d5b8e3636f4c3d71258033208a5bd9e</a><br>
<br>Will work on test.<br><br>Max <br><br><div class="gmail_quote">On Tue, Mar 30, 2010 at 10:25 AM, C. Titus Brown <span dir="ltr"><<a href="mailto:ctb@msu.edu">ctb@msu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Mar 29, 2010 at 07:37:35PM -0400, Max Laite wrote:<br>
> Hmmm well, seems that doing a test in run.py to see if a dbfile was<br>
> specified or not and passing that or :memory: may work?<br>
<br>
</div>Yep.<br>
<div class="im"><br>
> Seems too easy to be true.....I have it hard coded right now to just use<br>
> :memory: and it seems to be working. I see no files created like when we use<br>
> something.db.<br>
><br>
> How would we go about testing it?<br>
<br>
</div>Good question!<br>
<div class="im"><br>
> It doesn't change any output or create any output, you just pass :memory:<br>
> and that is it, sqlite takes care of everything in the back ground.<br>
><br>
> Would it be possible to do something where we create in-memory db, then do a<br>
> memory purge then see if its gone or not? Not sure it can be easily tested.<br>
<br>
</div>Probably the best way is to add some data into the db, then tell the<br>
current db to reopen itself (at which point all the data will be gone) and test<br>
to make sure we have an empty db.<br>
<br>
cheers,<br>
<font color="#888888">--titus<br>
</font></blockquote></div><br>