python-noob - which container is appropriate for later exporting into mySql + matplotlib ?

[someone]

On 04/13/2013 03:44 AM, Steven D'Aprano wrote:
> On Fri, 12 Apr 2013 23:26:05 +0000, Cousin Stanley wrote:
>
>>    The firefox browser keeps different sqlite database files for various
>>    uses ....
>
> Yes, and I *really* wish they wouldn't. It's my number 1 cause of major
> problems with Firefox. E.g.
>
> http://kb.mozillazine.org/Bookmarks_history_and_toolbar_buttons_not_working_-_Firefox

Oh, sorry to hear that... Actually I mostly use chromium (but I also 
have firefox installed). I just opened a few of my sqlite files from 
within sqlite3 - that was very interesting to see the contents of these 
files without being anything like a "hacker"... :-)

> Using a database for such lightweight data as bookmarks is, in my
> opinion, gross overkill and adds to the complexity of Firefox. More
> complexity leads to more bugs, e.g.:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=465684#c11
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=431558

On the other hand, I guess it's in the spirit of "open source" that it's 
easy for everyone to go in an see what's in the configuration files and 
(if one wants) modify and/or make own improvements/programs that tamper 
with these sql-files ?

> Please don't use a full-featured database if you don't need the overhead

Ok, you're saying there's overhead I should think of... Most of my 
programs are rather small in comparison with commercial programs so I 
think I don't have to worry about overhead (I don't have any real 
speed-critical applications).

> of ACID compliance. And if you do, well, Sqlite is not fully ACID compliant.

I just had to google what ACID compliance means and accordingly to this:

http://en.wikipedia.org/wiki/SQLite

"SQLite is ACID-compliant and implements most of the SQL standard, using 
a dynamically and weakly typed SQL syntax that does not guarantee the 
domain integrity."

So you seem to disagree with wikipedia?

I however don't understand what it means "to not guarantee domain 
integrity"... As I read this, I get the feeling that sqlite *IS* ACID 
compliant (wikipedia however doesn't use the wording: "fully ACID 
compliant", maybe this is the culprit) ?