Re: SQLite segmentation fault in DBI?

I'm not heavy into database stuff, but it seems to me that if you write with the DBD and DBI abstraction layers, you can swap between database engines fairly easily, without changing much in your code. Maybe look at On Databases and other similar ones.

Maybe your segfaults are coming from an improper installation or upgrade.... if you can, compile the latest sqlite libs and perl module and see if you get install errors.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku

Comment on Re: SQLite segmentation fault in DBI?

Replies are listed 'Best First'.
Re^2: SQLite segmentation fault in DBI? by derby (Abbot) on Jan 26, 2010 at 12:02 UTC
... you can swap between database engines fairly easily, without changing much in your code ... That made me chuckle. It's true in theory but a real huge pain in practice -- the database vendors have done their fair share of ensuring lock-in with proprietary extensions to SQL (and from what I remember, the DDL portions of SQL were never standardized - but it's been a while since I looked into it). -derby	[reply]
Re^3: SQLite segmentation fault in DBI? by dsheroh (Monsignor) on Jan 27, 2010 at 11:16 UTC
...which is why some of us stick to the SQL standard wherever possible, only gritting our teeth and cursing the database vendors, lo, unto the seventh generation, in those rare cases in which we have no choice but to blight ourselves and our code with their proprietary extensions. And then there are those who use ORMs to abstract it all away. Perhaps I just don't get heavy enough into the database side, but I find it pretty easy to write only cross-platform SQL.	[reply]