On 4/1/06, Noah <[EMAIL PROTECTED]> wrote: > I was wondering if there were any practical differences (other than > speed) ie features not working or working different based on whatever > db you use? Other than changes you might have to make to your SQL > statments?
I believe Django tries to take advantage of the different column types supported by the various databases; for example, an IPAddressField in a model will (or ought to) become an 'inet' column in PostgreSQL, but in MySQL will be a 'varchar' instead since MySQL has no native column type which exactly corresponds to an IP address. Beyond that, you shouldn't need to worry much; Django tailors the SQL it executes to suit the particular database backend you're using, so the only time you need to be careful is when you manually execute a query. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
