El 11/08/13 12:11, John Fabiani escribió:
On 08/10/2013 08:42 AM, Ricardo Aráoz wrote:
This is not only restricted to sqlite, I think this would affect
anyone using two datasets to perform a query. Once the data is inside
the data sets then it's the same no matter which db you are using?
If any of the DS is empty strange things happen. If tjtasDS is empty
it will do as shown, if the other DS is empty an exception will be
raised. Probably the fact that one of the DS would be empty was never
considered?
I could be wrong but I was under the impression that datasets (in
Dabo) were sqlite tables. That is why I asked if the same issue
occurred in a standard sqlite with the use of Dabo.
Johnf
I think they are tuples of dictionaries, with added methods and
properties, when you do execute() then it will use an in memory sqlite
to perform the query (at least that's how I think it works). So this
will affect queries between data sets that come from any data base.
This said I think it's not an sqlite issue given that when the "other"
data set (the one referenced in the cursorDict) is empty the results end
up inside the cursorDict, but when the "main" data set (the one from
which execute() is issued) is empty an exception is raised. It does not
sound like an sqlite issue.
But of course I'm telling you this without knowing the inner works of
Dabo at all.
Maybe someone with more knowledge of Dabo could set us straight?
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]
