Using this, would it mean that no file is generated in the file-system?
Does this mean that all that temporary-folder/file jazz would not 
be required?
In that case, you could even not have to clear-out the tables from 
the previous test-run, as there wouldn't be any, right?
But it should still require clearing-out data between-tests, right?
And what about the schema-log file? Would that still have to be created? It 
would seem redundant, as there would not be any use for it - unless 
consecutive-tests are modifying the schema, and committing.

How would the life-cycle of such a db-object be managed?

If every test re-launches the model that defines the db-object, than it 
would be created from scratch every time - in this case no schema-log is 
needed at all, but this could be slower computationally - though the lack 
of access to the file-system may override that shortcoming and actually 
make it faster(?)
And also conditional-schema-creation may improve performance as well, as 
because the db-schema is regenerated on each test, than each one could only 
construct the tables it actually needs.

If the db-object is reused across-tests, and conditional-schema-creation is 
applied, than how would the migrations happen? In this case it *would* need 
a schema-log, right? That may override the benefit of the 
conditional-creation, by having it need to access the file-system... So if 
the db-object is still reused, but no conditional-creation is applied, than 
it might take a bit more for the set-up faze, as it would generate all 
tables, but than a schema-log could really be un-necessary - this could 
give the best of both worlds - no re-creation of tables, AND no file-system 
access - right? Can that be accomplished? I mean, generally, the way to 
avoid using a schema-log, migrations are needed to be turned-off. But 
Wouldn't athat prevent the dal from being able to even create the tables in 
the first-place?


On Thursday, May 16, 2013 10:37:09 AM UTC-7, Anthony wrote:
>
> I'm not sure how you are goint to implement an in-memory 
>> relational-database that can be used woth the same db-object-using code - 
>> that sounds ineresting...
>
>
> db = DAL('sqlite:memory') 
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to