On 05 Jun 2007 16:40:32 +0200, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Joe Wilson napisał(a):
> At least there's a known workaround, so no problem.
Workaround is not a solution.
For an embedded (and lite) SQL engine like SQLite, you have to bear in
mind some features will never be implemented, but you can always open
a ticket and "lobby" for that feature to be implemented.
> You should ask for your money back.
Yes it's free. But I think that no user (or author) of software like when
software crashes. Unfortunatelly SQLite does.
I would agree with you that it is a bug if the the library crashes,
but I don't think there is any portable way for sqlite to know the
stack size (or available stack bytes), so it's that kind of error
SQLite simply can't do nothing about. To tell the truth, I don't know
of any easy non-portable way of doing it either in Windows or Linux.
You should file a bug report, anyway, because the developers know
better than me.
If for nothing else, it could be used to update the documentation
about unions to warn about this case.
Last time wasn't sent to the mailing list so once more:
Does anyone know other places apart from unions where deep recursion may be
used?
I believe your question is more for other places where you can avoid
the deep recursion (as the deep recursion will always lead to the same
problem).
Best regards,
~Nuno Lucas
----------------------------------------------------------------------
Kasia Cichopek eksponuje biust
>>> http://link.interia.pl/f1a6f
