Entries tagged: postgresql

  • #23

    Bookmark posted
    on 11. apr 2010 12:47

    Settling for NoSQL

    I think Bruce Momjian nails it:

    NoSQL databases differ in several ways from relational databases:

    • crude or no query language (clients do much of the processing normally done by SQL)
    • no joins (data must be joined client-side)
    • sacrifice ACID and transaction properties for speed, fault tolerance, or easy addition and removal of nodes

    Few are excited about losing these valuable relational database features, but if your query response and infrastructure requirements can't be met by relational databases, and you can accept these limitations (think social media sites or search engines), NoSQL makes perfect sense.

    I have not jumped on the NoSQL bandwagon yet, since I lack a good use case for it. For now, I’m quite satisfied with SQL.

    Visit: http://momjian.us/main/blogs/pgblog/2010.html#April_10_2010

  • #17

    Bookmark posted
    on 9. jan 2010 16:44

    PostgreSQL expert suggestions for Django

    Josh Berkus has some excellent suggestions on how Django could be improved to take advantage of PostgreSQLs capabilities.

    I find myself agreeing, and in particular with this:

    Allow the Use of Schema in Place of App Names: currently Django prefixes all table names with the "app name" resulting in table names like legacyauth_userpreference. This makes sense on databases with no schema support, but it would be great if, on Postgres, Oracle and other DBs with good schema support, Django would support replacing that "_" with a "." so that we could use real schema.

    Django’s current table naming scheme hurts my eyes, so this would be a definite improvement…

    Visit: http://it.toolbox.com/blogs/database-soup/stuff-id-love-to-see-from-django-36278

  • #15

    Bookmark posted
    on 19. nov 2009 17:30

    Comparison of different SQL implementations

    By fellow Dane, Troels Arvin:

    The following tables compare how different DBMS products handle various SQL (and related) features. If possible, the tables also state how the implementations should do things, according to the SQL standard.

    This is very thorough and interesting. It does a really good job of explaining why creating applications that run on multiple database platforms is a hard thing.

    It's encouraging to see that my favourite RDBMS, PostgreSQL seems to lead the pack (although it has a few transgressions of its own.

    There's little good to say about MySQL in this comparison. Several flagrant violations of the standard and slow to adopt new SQL features.

    Visit: http://troels.arvin.dk/db/rdbms/

  • #141

    Blog post
    by Mikkel Høgh
    on 13. oct 2008 03:13

    Drupal database performance: MySQL and PostgreSQL compared.