Re: Snowflake db backend

2021-12-04 Thread Tim Graham
Cedar Cares, Inc. funded me to write a Snowflake backend. The first alpha for Django 3.2 was released this week. Testers and feedback are welcome! https://github.com/cedar-team/django-snowflake https://pypi.org/project/django-snowflake/ I didn't find the implementation particularly onerous, but pe

Re: Snowflake db backend

2021-04-20 Thread 'Taylor' via Django developers (Contributions to Django itself)
Sorry, I meant to write Scott, not Tim. I shouldn't write emails late at night. - Taylor On Tuesday, April 20, 2021 at 10:29:46 PM UTC-7 Taylor wrote: > Hey Everyone, > > Sorry to open up an old thread. > > Tim - were you ever able to open source your Snowflake backend? We would > love to use

Re: Snowflake db backend

2021-04-20 Thread 'Taylor' via Django developers (Contributions to Django itself)
Hey Everyone, Sorry to open up an old thread. Tim - were you ever able to open source your Snowflake backend? We would love to use it and even devote resources (developers or funding for contractors) to improving it and getting the tests passing. At Cedar, we were planning on creating our own

Re: Snowflake db backend

2021-01-27 Thread Florian Apolloner
Hi Scott, Thank you for your response, this is very helpful. On Tuesday, January 26, 2021 at 11:38:18 PM UTC+1 foug...@apps.disney.com wrote: > Snowflake does not support lastrowid. So, we grab the last ID inserted > with a 'SELECT MAX(pk_name) FROM table_name'. This is obviously prone to >

Re: Snowflake db backend

2021-01-26 Thread Scott Fought
In order to release the code, I need to provide a sustainment plan per our open source committee. Which is why I was reaching out. I can share some of the challenges conforming Snowflake to the SQL model Django uses. It sounds like we may have had similar experiences writing backends, but pos

Re: Snowflake db backend

2021-01-23 Thread Florian Apolloner
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

Re: Snowflake db backend

2021-01-22 Thread Tom Forbes
ocs to link to the package though. >>> >>> On a side note, is Snowflake fast enough for general purpose web apps? When >>> we evaluated it the performance characteristics where similar to Redshift, >>> optimised for large analytical aggregation rather than fast, s

Re: Snowflake db backend

2021-01-22 Thread Tim Graham
terest it might be considered for inclusion. >>> We could definitely update the docs to link to the package though. >>> >>> On a side note, is Snowflake fast enough for general purpose web apps? >>> When we evaluated it the performance characteristics wh

Re: Snowflake db backend

2021-01-22 Thread Scott Fought
mance characteristics where similar to >> Redshift, optimised for large analytical aggregation rather than fast, >> smaller result sets typically seen with Django apps. >> >> Tom >> >> On 22 Jan 2021, at 21:49, Scott Fought wrote: >> >>  >> &g

Re: Snowflake db backend

2021-01-22 Thread Adam Johnson
rpose web apps? > When we evaluated it the performance characteristics where similar to > Redshift, optimised for large analytical aggregation rather than fast, > smaller result sets typically seen with Django apps. > > Tom > > On 22 Jan 2021, at 21:49, Scott Fought wrote: >

Re: Snowflake db backend

2021-01-22 Thread Tom Forbes
evaluated it the performance characteristics where similar to Redshift, optimised for large analytical aggregation rather than fast, smaller result sets typically seen with Django apps. Tom > On 22 Jan 2021, at 21:49, Scott Fought wrote: > >  > We have written a Snowflake DB bac

Snowflake db backend

2021-01-22 Thread Scott Fought
We have written a Snowflake DB backend that we use internally in several projects and are considering releasing it for public use. My preference would be to incorporate it as a core backend so the nuances of Snowflake SQL are considered when changes are made to the core system. Is this