-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/25/2011 08:56 AM, Richard Hipp wrote: >> Thanks for the helpful feedback. Please let us know if you find this >> solution inadequate or if you encounter other problems.
A far better solution to this kind of thing is to do them the other way round. ie the custom VFS you are doing subscribes to sync notifications rather than them being hurled at existing ones without warning. Either way isn't perfect, but opting in is far less likely to cause future compatibility problems than having to be prepared for the unexpected. The VFS version number is the existing method for opting in. A suggested totally clean and compatible way of achieving your goals would be to bump the VFS version number to 3 and then call the existing xSync method with SQLITE_SYNC_OMITTED. V2 and earlier VFS will never see this new mechanism and everybody will be happy including me :-). No existing code will be surprised either. If it remains a file control then I will need a table in my code saying ops having an error is normal and which aren't since the latter should turn into exceptions and the former not. Fortunately this one won't happen that often. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0/rw4ACgkQmOOfHg372QRmIQCgxejja5bgcIxzyADc17rFIaiY fjkAoIp9CqKhC9fjfNe7yu56pIV6dni2 =6RsW -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
