-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Django 1.7 #15
Comments
any update on django 1.7 ? |
@Alir3z4 not yet, but i'm happy to take pull requests. its a good way to learn about django and django-nonrel 😄 |
@aburgel Great, I haven't tried to merge/upgrade django changes to django-norel yet.
Basically these are my main questions, which it's a lot, but if I get them answered I can be really active on upgrading django changes into django-nonrel since I have good amount of free time to contribute. I'm using django-nonrel on a active project with MongoDB and having it upgraded to the latest is my highest priority. Thanks |
@Alir3z4 I created a To start your work, you should take a look at what I've merged into 1.6. (All except the merge commits). https://github.com/django-nonrel/django/commits/nonrel-1.6?author=aburgel You can cherry-picking those changes over into your new branch. Most of them should work without much difficulty. You will also probably need to change djangotoolbox, and probably mongodb-engine as well. For 1.6 most of the changes were pretty minimal, mostly updating method signatures. Once you've got something working, however minimal, open up a pull request and I'll help out with some comments, and if I have time, some code as well. I would also read through the 1.7 release notes as a guide to what you might want to test as you're making changes. |
@aburgel Thanks for detailed explanation. It's great. I already forked the project and ran the test suite of django 1.7 with all its dependencies, the result of running test suite is :
I'm gonna keep that result to check for after applying nonrel changes, also I just applied 3427662 and I got some conflicts which seems to be pretty easy to solve. I'll keep you this thread updated about the progress. Thanks again for the help. |
cool. a bunch of those failures are probably expected since django nonrel doesn't support a lot of the queries that are used in the tests. |
@Alir3z4 Do you have any stable version of 1.7 atm? |
@namlehong I tried to get django-norel working with 1.7 but I get into lots of errors and issues that I couldn't get it working easily. Where my working nosql database is MongoDB and I would get many issues there too. I haven't tried to work on the upgrade. As now Django latest release is 1.8. Unfortunately I see no news about nosql support on Django upstream even in their 1.9 notes. I'm afraid by keeping a fork such as django-nonrel, django upstream is loosing interest in matter of any work on NoSQL on their part. Although I can see recently they work on making database part more modular but after having migrations things got more frustrating. Where most of django core might bring the @aburgel while working on upgrading to latest django would you consider some getting some activities and talk with django upstream about getting nosql into core ? I know this has been done couple of years ago seriously but well django core has changed a lot since. Today I was looking at https://code.djangoproject.com/ticket/19009 and notices the ticket was closing about 2-3 years ago. I think if we do some updates on the ticket and similar ticket won't hurt anybody, at least nonrel users such as me would know about the feature of nosql and django core. I'm trying to prepare a update on that ticket that I highly appreciate your( @aburgel ) and others who can add or correct the below ticket response before its submission.
Please let me know how I can make a better ticket response, I'm asking since I don't want to make a wrong statement. |
@Alir3z4 my advice would be to not try to get mongo support into django official, but to try to get in whatever minimal set of changes needed to support the nosql databases using djangotoolbox. the changes are pretty minimal for most nosql databases. mongo is a bit unusual because it uses a non-integer object key, and most of django assumes that primary keys are integers. so that will take some extra work. |
The text was updated successfully, but these errors were encountered: