What about AUTOINCREMENT for integer keys??

[reflectivist]

One feature I rely on is the AUTOINCREMENT feature, and I can't find any support for that in the documentation. Is it there? I hate to have to create my table definition uses SQL strings just for that.

[stephencelis]

It's there: 798ee8e

[reflectivist]

OK, after reading the AUTOINCREMENT description again, apparently it's got high overhead and is usually unnecessary and the default behavior is sufficient, probably for my needs. I will try it out without autoincrement and then use it if necessary. BTW: GREAT job on this API. Really fantastic/prodigious, timely, convenient, complete, etc... major kudos.

[stephencelis]

Yep, avoid AUTOINCREMENT unless you really need it!

And thanks! Glad you like it :)

[reflectivist]

Yes. Compared to ugly libsqlite and Objective C which I used to use, this is far cleaner, makes easier to read more maintainable code, and it actually works!

[ericcgu]

Stephen Celis is the man.

On Fri, Jan 30, 2015 at 12:40 PM, reflectivist notifications@github.com
wrote:

Yes. Compared to ugly libsqlite and Objective C which I used to use, this
is far cleaner, makes easier to read more maintainable code, and it
actually works!

—
Reply to this email directly or view it on GitHub
#55 (comment)
.

[stephencelis]

😊