Hi all,
Here’s an issue of usability that if fixed could make usage of custom fields
simpler.
Right now fields don’t allow a built-in defaults, and you need to explicitly
set the default parameter for model fields. The problem is that this adds a
ton of boilerplate code.
Using the Polls tuto
Hi Mark,
Maybe the work done to support Google App Engine and its Datastore could
also be useful for you. You can find more information about that project on
https://github.com/potatolondon/djangae and
http://djangae.readthedocs.org/en/latest/db_backend/
Cheers,
Goetz
--
You received this messa
On 14 juin 2015, at 20:23, mnunberg...@gmail.com wrote:
> It would only be worthwhile trying to make a proper database-engine if the
> rest of django would support it: Specifically, any kind of data modification
> using SQL is currently unsupported
This is an well defined limitation. If you can
Thanks for the advice. I imagine the emailer example is a way to show how to
make something that’s not really a Django model into a Django model (similar to
what Cassandra does).
Interesting point about not supporting the ecosystem - but the question is how
much of the ecosystem (rough estimate
Some more data points (to support removing 3.3 support):
I believe old versions of RHEL were the reason people needed 2.6 support.
Unlike 2.6, I believe RHEL has never supported Python 3 except through
"Software Collections", and the Python33 software collection EOL is Oct
2016 (before 1.8 supp
