Re: [sqlite] sqlite Commit C API

> On Thu, May 17, 2012 at 7:04 PM, Rajesh Kumar wrote: > int fsync( int fd ) { return 0; } > > fsync will expect an Integer pointer right. But sqlite pointer is of type > sqlite3*. So how can fsync works on sqlite. What should I pass to fsync??? > > You don't need to call

Re: [sqlite] sqlite Commit C API

If you can run perl on your ARM host try this utility to see if fsync() actually works -- this is a real end-to-end test that you pull the plug on and it will let you know if your disk file is where it's supposed to be and how many errors you had. http://brad.livejournal.com/2116715.html

Re: [sqlite] sqlite Commit C API

On Sun, May 20, 2012 at 12:04:33PM +, Black, Michael (IS) scratched on the wall: > Another more indirect way to test is this utility: > > http://kerneltrap.org/mailarchive/linux-ext4/2009/3/22/5215824 > > Which...if your fsync doesn't work at all will return something really > close to

Re: [sqlite] sqlite Commit C API

Hmmm...our math is a bit different... A 1,000 RPM disk would take 1ms to spin around once (there are 1000ms in a second, correct?) 10,000 RPM would take .1ms. 7200 RPM would take .138ms And...if I reduce the buffer size to 1 byte I see this...around 2-3X of rotation time with the sleep

Re: [sqlite] sqlite Commit C API

Black, Michael (IS) wrote: > Hmmm...our math is a bit different... > > A 1,000 RPM disk would take 1ms to spin around once No it wouldn't. > (there are 1000ms in a second, correct?) Yes, but RPM stands for a revolution-per-*minute*. You are off by a factor of 60. --

Re: [sqlite] csv test cases (was Details On New Features)

Donald, I have a question about #9 of your test cases. According to RFC 4180, #9 is an invalid record. The RFC states "If fields are not enclosed with double quotes, then double quotes may not appear inside the fields." However, I imported your test cases into Open Office, Excel, and Numbers

[sqlite] SQLite related crash when starting Skrooge

Hi guys, I am one of the developpers of Skrooge, an Open Source application for personal finances management (http://skrooge.org). After upgrading SQLite to 3.7.12, our users report crashes upon starting the application : https://bugs.kde.org/show_bug.cgi?id=300183 Apparently, switching back

Re: [sqlite] SQLite related crash when starting Skrooge

On Sat, May 19, 2012 at 3:35 PM, Guillaume DE BURE < guillaume.deb...@gmail.com> wrote: > Hi guys, > > I am one of the developpers of Skrooge, an Open Source application for > personal finances management (http://skrooge.org). After upgrading SQLite > to > 3.7.12, our users report crashes upon

[sqlite] 3.7.12: segmentation fault in sqlite3ExprCodeTarget() when called from gnome-shell-3.4.1

(As reported at https://bugs.gentoo.org/show_bug.cgi?id=416563; originally sent to sqlite-dev, but an sqlite-dev list member informed me that I should report the problem to this mailing list instead.) After updating to sqlite-3.7.12, I have been getting crashes in gnome-shell-3.4.1 a few seconds

Re: [sqlite] 3.7.12: segmentation fault in sqlite3ExprCodeTarget() when called from gnome-shell-3.4.1

On Sun, May 20, 2012 at 3:04 PM, Alexandre Rostovtsev wrote: > (As reported at https://bugs.gentoo.org/show_bug.cgi?id=416563; > originally sent to sqlite-dev, but an sqlite-dev list member informed > me that I should report the problem to this mailing list instead.) > >

Re: [sqlite] sqlite Commit C API

On Sun, May 20, 2012 at 01:26:48PM +, Black, Michael (IS) scratched on the wall: > Hmmm...our math is a bit different... Yeah, your math is wrong... 8-) > A 1,000 RPM disk would take 1ms to spin around once A 1,000 RPS disk would, but not a 1,000 RPM disk. > I believe my original