NULL causes "crashed table" report

[Jon R]

Thanks to an error in a query I was running, I was accidentally trying to insert NULLs into the OQGraph table. However, it took me a while to figure this out as the INSERT statement was failing with a warning that the table was in a "crashed" state (which had me off looking for problems with the creation of the table in the first place).

IMHO, a friendly approach would just be to just treat all node columns as NOT NULL and throw that type of error instead. Assuming, of course, it's not a huge PITA to fix.

Other than a desire for more types of graph queries (betweeness, centrality, other shortest path algorithms, etc.) to work with, this plugin is brilliant! Thanks.