Get MonetDBlite test suite working (tests/test_lite/test_pylite00.py) about monetdbe-python HOT 8 CLOSED

should be handled at the python side. ie first monetdb.sql should open an in memory db and keep this available. But normal behaviour would be for the user to open a db (connect)

from monetdbe-python.

sure, but then why close this issue? Also, I',m not sure if we are talking about the same issue.
what I try to say is that the old monetdbelite behaviour is to allow only one DB open, and any new SQL call will be executed on the current connection. Question is if we want this behaviour? I find it quite confusing. Also, monetdbe, until yesterday, supported multiple open connections. This is incompatible with described functionality. From a user perspective I would highly recommend to allow multiple open connections

from monetdbe-python.

I thought I still allow multiple connections (you just have to pass the same connection information).

from monetdbe-python.

Only multiple databases is not supported now!

from monetdbe-python.

The old sqlite behaviour should go, I think. The new interface is clean enough. A user should open a database always.

from monetdbe-python.

No monetdblite compability. remainder moved into separate issue.

from monetdbe-python.

Still, there are some lite tests that might be testing some interesting edge cases. I'm going to reopen this issue and rename it.

from monetdbe-python.

This has been fixed

from monetdbe-python.