ah, the field that is causing trouble is declared as VARCHAR. sqlite2 dumps some rows as integers, others as strings

sqlite3 dumps them all as strings, but turned the large unsigned into a double on read

(and dumped it as '1.84467440737096e+19'

)

we had a python script dump the sqlite2 db, process the output, then import to sqlite3

I am thankfully ignorant of the details of getting that working

yeah, I can now see why that was needed.

[illumos-gate] 15167 Panic when halting a zone with self-created links -- Andy Fiddaman <illumos⊙fn>

Assuming both the 2 and 3 shlib can be linked at once, I think we would probably aim for a C program that does the conversion and any checks, etc.

SQLite3 is pretty great, it would be good to ditch the old stuff.

Just to make it trickier, there are two other consumers of SQLite 2 in illumos-gate: idmapd and smbsrv's libsmb

and the version of sqlite 2 in the gate has been extended with UTF8 case conversion functions (used by idmap in sql constraints)

it'd be nice.. i'm pretty sure there's a lurking consistency bug in the current version that leads to corrupt repository.db files during unclean shutdowns

I have done a million unclean shutdowns of late without corruption

but that doesn't mean much, except it's hard to trigger

sommerfeld: We may be able to assemble a framework to do all three of those conversions in at least a broadly similar fashion