SQLite and Android N (2016)

Re:SQLite and Android N (2016) by amluto on Friday January 27, 2017 @08:28AM (#13499624)

One big danger seems to be that POSIX locks don't like having two fds for the same file in the same process. But Linux has a newish kind of lock that is backwards-compatible and works better. I would love for SQLite to use it.

Does SQLite accept patches?

[ Parent | on HN ]

Re:SQLite and Android N (2016) by kiallmacinnes on Friday January 27, 2017 @08:41AM (#13499697)

Patches are accepted, though.. SQLite is, by all accounts I've read, a very well written and tested piece of software, and I'd be surprised if there was an easy and safe win like this which hasn't already been proposed / considered.

Though, my guess shouldn't stop you looking for previous suggestions to implement this, and if there are none, submitting it yourself :)

[ Parent | on HN ]

Re:SQLite and Android N (2016) by stuaxo on Friday January 27, 2017 @11:01AM (#13500524)

It's amazing how many quick wins are to be had in open source if you have the time to patch yourself.

[ Parent | on HN ]

Re:SQLite and Android N (2016) by pjmlp on Friday January 27, 2017 @08:45AM (#13499731)

POSIX locks semantics are implementation defined, hence why they are pretty much useless unless all applications access the same set of files play by the same rules.

[ Parent | on HN ]

Re:SQLite and Android N (2016) by zurn on Friday January 27, 2017 @08:55AM (#13499776)

Or the apps all know which implemnetation they are running on (Linux in this case).

[ Parent | on HN ]