SitePoint Sponsor

User Tag List

Results 1 to 6 of 6
  1. #1
    .* draziW tnioPetiS *. bronze trophy
    Join Date
    Jun 2004
    Location
    "Then I figure the most good good guy will win."
    Posts
    1,666
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Djago: Database questions...

    Hi,

    Django users... What DB do you choose to use? Looking at this thread PostgreSQL looks like the more popular choice... but why?

    The Django documentation/FAQ states:

    If you want to use Django with a database, which is probably the case, you'll also need a database engine. PostgreSQL is recommended, because we're PostgreSQL fans, and MySQL and SQLite 3 are also supported.
    Being "a fan" does not really tell me why it is the better choice...

    Any thoughts?

    TIA,
    Cheers,
    Micky

  2. #2
    .* draziW tnioPetiS *. bronze trophy
    Join Date
    Jun 2004
    Location
    "Then I figure the most good good guy will win."
    Posts
    1,666
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Well, I guess comment #7 on this page kinda explains the reason why PostgreSQL is recommended...

  3. #3
    SitePoint Wizard bronze trophy KevinR's Avatar
    Join Date
    Nov 2004
    Location
    Moon Base Alpha
    Posts
    1,053
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    you should have posted this in the database forum.

  4. #4
    .* draziW tnioPetiS *. bronze trophy
    Join Date
    Jun 2004
    Location
    "Then I figure the most good good guy will win."
    Posts
    1,666
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by KevinR View Post
    you should have posted this in the database forum.
    Sorry...

  5. #5
    SitePoint Wizard Rick's Avatar
    Join Date
    Oct 2002
    Location
    Lancashire, UK
    Posts
    3,847
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    No need to be sorry, not a problem Have moved this to databases.

    PostgreSQL is a much more enterprise ready database than MySQL. I've used MySQL and PostgreSQL along side each before for evaulation, and I've always found that Postgres is a much more solid and reliable database when compared to MySQL.

    Its also has a more complete feature set and stricter (i.e. better) handling of constraints and datatypes. To a new developer this might seem a headache, its easier to get things to 'just work' in MySQL, PostgreSQL requires more DBA skills to get setup and to get your databases working correctly - someone new to development might see this as being a bit of a pain in the ***.

    However in the long run a steeper learning curve is well worth it if you think your application will grow in the future and your requirements will become more complex. The time saved initially with MySQL will often be needed later to compensate for some of its quirks.

    MySQL has a speed advantage for simpler queries, however this gets quickly eroded when you need to perform more complex queries and transformations down the line.

    In short: MySQL is a friendlier database, its easy to setup and very easy to learn to work with. However it lacks features that DBMS like PostgreSQL offer, whether or not you need this features is a question you should try to answer when designing your application.
    Rick

  6. #6
    .* draziW tnioPetiS *. bronze trophy
    Join Date
    Jun 2004
    Location
    "Then I figure the most good good guy will win."
    Posts
    1,666
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Rick! You rock! Thanks for that great reply, it has really helped clear things up.

    TBTH, I like strictness... Not that I am the best coder in the word, but I hate sloppy coding. Sounds like the learning curve for me is definitely worth it.

    Thanks again Rick, I greatly appreciate you sharing your knowledge.

    Cheers,
    Micky


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •