On 29 Apr 2015, at 9:21am, Scott Robison <scott at casaderobison.com> wrote:
> Personally I don't see it as a bug. A limitation, yes. A different > algorithm that requires less ram would remove / change the limit. Anything inside the SQLite code which causes a Segfault is a bug. Assuming that you're not hacking your OS or messing with SQLite 'black box' variables like connections and statements. Just my humble opinion. I'm not on the development team. A minimal (either small, or simple to reproduce) repeatable example would be welcome. It can even include huge data as long as you can describe a way to create crashing data like "Generate a trillion identical rows in this table.". Simon.