On Thu, May 15, 2008 at 10:25 AM, Amit Ramon <[EMAIL PROTECTED]> wrote: > Now, if I subclass an existing field and I want to define the database type > myself, how do I do that? Is there a place to add mapping between a name > returned by get_internal_type and a database type, like in creation.py?
Well, there are two ways to do it. First, like you now know, get_internal_type() is preferred, if there's an existing mapping that suits your needs. That allows the field to be used with multiple databases, which is a big plus. On the other hand, if there's no existing mapping that's appropriate for you *and* and you know for a fact that you won't be distributing this code, then you can write a db_type() method instead. It returns a string that's used to create the column in the database directly. Internally, db_type() is where Django does the get_internal_type() mapping, so it providing your own db_type() will completely replace that process. Unfortunately, using db_type() means your field will be tightly coupled to a specific database implementation. If you're only working on your own stuff that will never be released, that may be fine. But keep in mind that it also means you can't, for instance, use SQLite in development and PostgreSQL in production; at least, not without either changing code between the two, or writing your own code to determine which environment is being used. All this makes db_type() a bit tricky to work with, so only go there if you're sure you need it. -Gul --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
