Hello everyone, I am a participant in the Summer of Code 2007 and working on "Implementing Check Constraints in Django". My mentor is Simon Blanchard.
The hosting page for the projects is at http://code.google.com/p/django-check-constraints/ and the Proposed Features Wiki at http://code.google.com/p/django-check-constraints/wiki/Features As you can see from the features page on the wiki, implementing check constraints will actually reduce the need for writing validators (all you require is to add the constraints in the models). Since the constraints are being implemented at the database-level it provides for better data integrity. Lately, I have been studying Django's API and have realized that most of the foundation is already present for me to work on( I would like to thank Adrian, Jacob and all the developers of Django for this). For my project,all that I have to do is actually append the sql statements for the table (containing the check statements) when syncdb is called. My problem is a typical one that "There is more than one way of doing it" Here's how I believe I might be able do it... 1) By creating a Check Field (that inherits the Field from django.db.models.fields) and getting things done. So I might have to make a few changes in the django.core.management [precisely in the _get_sql_model_create function and not to forget the data_types] 2) As proposed by my mentor by getting it done from the django.db.models.options file. So which is the best method to go about this problem (even if one doesn't exist in the list above, please suggest)? Thanking You Thejaswi Puthraya --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
