Hi Michael and All,
> On 3/8/07, Michael Bayer wrote:
> > but the point is, and why its "irrelvant" to me as the maintainer of
> > SQLAlchemy, is that this is totally an issue with sqlite, and has
> > nothing to do with SQLAlchemy. you should ask on their mailing list
> > about this particular b
Hi Michael,
On 3/8/07, Michael Bayer wrote:
> but the point is, and why its "irrelvant" to me as the maintainer of
> SQLAlchemy, is that this is totally an issue with sqlite, and has
> nothing to do with SQLAlchemy. you should ask on their mailing list
> about this particular behavior.
Sorry, I
On Mar 8, 2007, at 5:14 PM, Andrea Gavana wrote:
>> so, its all deleted. filesize is irrelevant.
>
> Uhm, really? What happens if Windows is saying that the filesize is 4
> GB of empty things? I told you I know next to nothing about database,
> but it seems a bit odd to me that the file size co
Hi Michael and All,
thank you for your detailed answer, and to have tried the demo I
have attached. I understand what you meant and you are perfectly
right, but if I can bother you with another small question:
On 3/8/07, Michael Bayer wrote:
> z-eeks-Computer:~/dev/sqlalchemy classic$ sqlite
setting the newDataBase flag to False, heres the echo at the end:
2007-03-08 14:30:26,428 INFO sqlalchemy.engine.base.Engine.0x..50 BEGIN
2007-03-08 14:30:26,435 INFO sqlalchemy.engine.base.Engine.0x..50
DELETE FROM treenodes WHERE treenodes.node_id = ?
2007-03-08 14:30:26,441 INFO sqlalchemy.en
Hi Michael,
On 3/8/07, Michael Bayer wrote:
> have you verified that the tables have been deleted from ? if the
> filesize doesnt shrink, that may be an artifact of sqlite's
> implementation.
Thank you for your answer. Well, I can reproduce it in a small Python
script that I attach to my email.
On Mar 8, 2007, at 10:08 AM, Andrea Gavana wrote:
> By printing the node names, I know that bad_node is no more there, but
> its data seems to still live in the database. I mean, even if I delete
> *all* the items, the database size is still 180 Kb, no matter how much
> I flush(), clear(), close
Hi Svilen,
first of all, thank you for your answer.
On 3/8/07, svilen wrote:
>
> This is the db-file size, which is actual DB-implemenation detail, and
> which will probably only grow up - depends on the particular db u
> have. There are many strategies, like paging etc. e.g. some DBs
> requ
This is the db-file size, which is actual DB-implemenation detail, and
which will probably only grow up - depends on the particular db u
have. There are many strategies, like paging etc. e.g. some DBs
require a whole partition just for themselves - dont even think of
shrinking those...
See you
