Hi Simon,
thanks for your hint. I needed some time to figure out, how to use this
mailing-list and I hope, you will get my answer.
I tried the same im MySQL and it worked -- I know, that is no reason I
just wanted to say.
I also tried, to rename one of the depth's to depth1 -- and then it also
worked in SQLite so thanks for the hint.
> Argh. An example where doing the work in your software rather
> than a huge SQL statement might be more understandable,
> both in your debugging and if anyone else ever has to read
> your code. Another way to simplify things might be to
> define your sub-select as a VIEW.
This comment of your I did not understand what you mean, maybe because
of my bad english? Sorry. If I got you right, you suggested not to use
such big SQL-Statements? I see that they are not ideally to debug but on
the other hand I also dont understand, why I should make thinks simpler
just to have afterwards some things to do in my program? I thought, the
SQL-System might be faster in data-filtering than my application...?
Best Regards,
Tobias
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
