Am 05.12.2010 10:41, schrieb Alan Gauld:
"Jorge Biquez" <jbiq...@icsmx.com> wrote
Talking with a friend about what he will do (he use C only) he suggest
to take a look on dBase format file since it is a stable
True enough and Dabo is worth a look since it provides not only a dbase
format db engine but a good GUI builder tool too.
However....
(Berkley) database file format (I hope I understood this one
correctly) . Plain files it is not an option since I would like to
have option to do rapid searches.
Why not use SQL?
SQLlite comes with Python, is small, easy to use and if necessary can be
used in-memory and as such fast.
Once you have decided to go down the database route then not using SQL
nowadays is a very odd decision. Its rather liike going out looking for
a car that has solid types instead of pneumatics. Why would you want to?
The NoSQL databases seem to be en vogue. Some big internet companies
have started to use them, like Google with its Big Table. That's how I
stumbled across them. There're a lot of discussions going on on the
internet which is better for which use case. There're some cases where
one kind of the database type is the clear winner, but most use cases
can be modelled with both.
My conclusion and what draw me finally to MongoDB over PostgreSQL and
SQLAlqemy was:
1) Really the ease of use (from setting up the database and later when
it comes to administration and scaling, which is particularly easy).
MongoDB is very useful for prototyping.
2) I don't need complex transactions and the ability to perform complex,
not in advanced known queries.
I'd say SQL-DBs are more sophisticated but more complex to use. For the
sake of learning, go with SQL. It doesn't hurt having a driver license.
If you need to go to the bakery around the corner the driver license
doesn't prevent you to jump on your bicycle.
Cheers,
Jan
HTH,
_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http://mail.python.org/mailman/listinfo/tutor
