Re: Snowflake db backend
On Saturday, January 23, 2021 at 12:41:35 AM UTC+1 t...@tomforb.es wrote: > > Honestly, I don't think we'd release this as a third party package. We > have had to code around a lot of core db specific code to get Snow SQL to > work > > This is good feedback that is valuable for us to hear. Even if you don’t > release it as a fully maintained package just understanding the pain points > you encountered while developing this is great feedback that can help us > improve. > > Would you be willing to share specific code snippets here, or just general > areas that you found challenging while developing this backend? > +1, if it were possible to show the full code (even if you are not going to maintain it in the longrun) would be very much helpful to improve. Like Tim I wrote one or two database backends in the past (informix and the likes) and it was not to bad. That said, mine where relatively easy to implement due to their closeness to existing database and (somehwat) conformance with SQL standards. I'd love to see the code for snowflake and maybe we can identify a few areas that would need improvement. Cheers, Florian -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fdd01c9d-041f-4206-b529-701fde694202n%40googlegroups.com.
Miss order and choices fields in Django values
Dear Django Developers:
I am a python developer. I have been using a django framework from the past
year.
I found that there are some problems in *values* method and this is the
description:
1. *Miss order *of fields in querySet if I make *myquery =
MyModel.objects.values('field1','field2','field3')* when I *print
QuerySet it give me
[{'field2':'data','field1':'data','field3':'data'},...]*.
so this miss order will cause a problem at *Union *of queryset
2. if the *field is choices* at model then *values(...) will give me
the key of a dictionary instead of its value *this is true but if I
display the query set to a user in a table .
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/961ee21f-b7d5-4655-914c-a55ba863d43dn%40googlegroups.com.
First time contribution
Hello, I’m a beginner in open source. I hope to contribute in Django community. I have been working with Python and Django for a year now. Can someone please guide me as to how to go about contributing. It would help me a lot. Thanks , Srijita -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8e583ff8-b75c-42d9-8e04-cf385315ceeen%40googlegroups.com.
