Re^2: perl database question

i see that crystal balls had been dusting them selves. the cvs , tvs, -> these type of files are NO GO. SOL would be nice but RDBMS still comes into consideration. i thought i was clear enough when i defined gadfly, but now it looks like i wasn't, sorry -> nasty habit. so as i said i need something that is like perl module (meaning inside of perl - that doesn't require separate installation procedure and configuration like mysql -- for example), and that acts as database engine. meaning that i can query large tables(several gb), connect data from different tables and insert data into new tables. i would have only one db, and only my application would move around it. so as i said i need db engine like mysql but that can contain only one database, several tables, can do searching through tables, does not have that silly 'connect to the database' procedure, it is fast(at least as mysql) and deals well with very very large data.

am i asking too much ?

SQLite looks promising but i still have to read the whole documentation

anyway thanks

Comment on Re^2: perl database question

Replies are listed 'Best First'.
Re^3: perl database question by runrig (Abbot) on Apr 26, 2008 at 23:02 UTC
...does not have that silly 'connect to the database' procedure,... I'll second (or third or fourth) the motion for (DBI and) DBD::SQLite. Yes, you have to install the module, but it's not the sort of big database engine comparable to Oracle, Sybase, or even MySQL. And you do have to go through the motions of connecting to the database, but that is because it's accessible through the perl DBI module (after all, you have to tell DBD::SQLite where your database file is somehow), and DBI is the standard way to 'connect' to almost any SQL database. It should be an easy module to install, and IMHO SQLite is the reason that perl doesn't need anything like Gadfly (or at least there is very little need). There was some activity to make a pure perl database sometime ago, but it kind of died out, and SQLite fulfills most of the need for that sort of module.	[reply]

Replies are listed 'Best First'.

Re^3: perl database question
by runrig (Abbot) on Apr 26, 2008 at 23:02 UTC

...does not have that silly 'connect to the database' procedure,...

I'll second (or third or fourth) the motion for (DBI and) DBD::SQLite. Yes, you have to install the module, but it's not the sort of big database engine comparable to Oracle, Sybase, or even MySQL. And you do have to go through the motions of connecting to the database, but that is because it's accessible through the perl DBI module (after all, you have to tell DBD::SQLite where your database file is somehow), and DBI is the standard way to 'connect' to almost any SQL database. It should be an easy module to install, and IMHO SQLite is the reason that perl doesn't need anything like Gadfly (or at least there is very little need). There was some activity to make a pure perl database sometime ago, but it kind of died out, and SQLite fulfills most of the need for that sort of module.

[reply]