Re: SQL ALchemy support on django
Hi, I failed to apply for gsoc, but I planned to give some effort on this whenever I get some time. Anyone having interest and time could help he with some tecnical guidence. Much more to do there. Thanks https://github.com/TrendBreaker/django-alchemy On Friday, March 4, 2016 at 2:00:11 PM UTC+6, Asif Saifuddin wrote: > > Hi, > > I will be working on preparing a proposal for sql-alchemy support on > django. [thorugh model meta]. > > Thanks > > On Wednesday, September 16, 2015 at 2:35:15 PM UTC+6, Asif Saifuddin wrote: >> >> Hi, >> >> >> How much difficult it will be to add SQLalchemy support to django? what >> are the technical difficulties? And which are the ways to add sqlalchemy >> support to django? >> >> As SQLalchemy is separated in core and orm will it be wise to use >> sqlalchemy core as the backend for django orm? Or through the meta api? >> any suggestion or direction to the solutions? >> >> The available 3rd party packages seems to be incomplete. >> >> >> Regards >> >> Asif >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e08e4be5-372e-4a8c-8505-f1e2fa91ef57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Using "py2" Trac keyword to tag Python 2-specific issues
I've started tagging Python 2-specific Trac tickets with the "py2" keyword. You can view such issues using: https://code.djangoproject.com/query?status=!closed&keywords=~py2 Since Django 1.11 will be the last version of Django to support Python 2, my plan is to close these issues if they don't receive any attention by the 1.11 beta release, scheduled for February 20, 2017. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/028810c9-3e08-4082-9e9a-1a5ece1b96b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Using "py2" Trac keyword to tag Python 2-specific issues
Hi Tim, If you need help while removing support of python2 from code base you could knock me. Thanks On Tuesday, May 31, 2016 at 12:34:23 AM UTC+6, Tim Graham wrote: > > I've started tagging Python 2-specific Trac tickets with the "py2" > keyword. You can view such issues using: > > https://code.djangoproject.com/query?status=!closed&keywords=~py2 > > Since Django 1.11 will be the last version of Django to support Python 2, > my plan is to close these issues if they don't receive any attention by the > 1.11 beta release, scheduled for February 20, 2017. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/56f6a134-dbea-470b-9266-0ca3a61f6fc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Possible Bug (MYSQL)
Hello,
I would like some help from the core guys. I'm getting an error while
executing the following query (the objective of this query is basically get
the last created employee for each company):
*Company.objects.annotate(Max('employee__pk')).filter(employee__pk=F('employee__pk__max'))*
The error follows:
*OperationalError: (1054, "Unknown column 'T3.id' in 'having clause'")*
Not sure if my query is correct in the Django perspective but it's look OK
when looking at DB level. There are some gotchas I noticed:
1 - It works in SQLite.
2 - If I change the field (eg: `*employee__pk*` to `*employee__created`*)
it works fine. It seems to crash only when using PK.
4 - The generated SQL does not include the `T3.id` in the `SELECT` clause.
If I add it through the `QuerySet#extras` the problem goes away.
Thanks in advance,
Paulo Poiati
blog.paulopoiati.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CABqSV%3DKz3CLzbQqxGOZ5FWtiuSy6soRi_3BXL0qpjtBFUSOh5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
