Re: [sqlite] External advisory locking ...

operations through an external server) via filesystem MAC mechanisms on an EAL-5 secure operating system (STOP OS). Hence the headaches. -Mike Ashmore On May 19, 2006, at 10:32 AM, [EMAIL PROTECTED] wrote: Mike Ashmore <[EMAIL PROTECTED]> wrote: Hello all, I'm working on a syst

[sqlite] External advisory locking ...

be keeping track of as well? Won't a given database file span quite a few inodes? Since locking will require me to invoke (slow) IPC mechanisms, I don't want to send any more lock messages off to my lock server than absolutely necessary; any suggestions on how I should approach that? Thanks in advance for any help you folks can offer on this problem. -Mike Ashmore

[sqlite] Programmatic notification of BEGIN TRANSACTION?

Is this possible short of mucking around in the VDBE? And if VDBE- mucking is required, does anybody want to offer any pointers? Thanks, -Mike Ashmore

Re: [sqlite] How to compile sqlite3 C sample code

n). A complete makefile might be as simple as the following line: LDFLAGS = -L/usr/local/lib -lsqlite3 Then, just 'make t' should compile and link your test program correctly. HTH, -MIke Ashmore

Re: [sqlite] GUID in place of AUTO_INCREMENT

le-column and follow a reasonable naming convention. At any rate, Dr. Hipp's suggestion of the AFTER INSERT trigger was exactly what I needed. Thanks! -Mike Ashmore

[sqlite] GUID in place of AUTO_INCREMENT

anybody care to work with me on creating one? And in any case, am I about to do something that was tried before, found to be a bad idea, and maybe replaced with a better idea? GUIDs tend to smell like bad design to me, but I can't seem to think of any alternatives. Thanks, -Mike Ashmo

Re: [sqlite] PRAGMA table_info oddness

Well, it's not the prettiest thing in the world, but it definitely works. Brilliant! Many thanks for your help, -Mike Ashmore On Jan 23, 2006, at 1:01 PM, Kurt Welgehausen wrote: Sorry, I didn't read your code carefully enough the first time. Your approach won't work becaus

Re: [sqlite] PRAGMA table_info oddness

oo", the origin column in the resulting view has (according to PRAGMA table_info(foo)) a 'NUMERIC' affinity. What I'd like is for table_info to report the origin column's affinity as TEXT. So, now that I've got my semantics sorted, does anybody have any suggestions for how to make that happen? Thanks, -Mike Ashmore

[sqlite] PRAGMA table_info oddness

o integrate the composite view into a Ruby on Rails application, and RoR seems to rely on the type reported by the table_info pragma to determine what format to use when updating or inserting records [1][2]. I've determined this happens with SQLite 3.2.8 and below; I have not yet tested ag