Hey everyone,
I’ve been playing around with the new AppEngine 1.7.3 release, and I noticed they’re switching to SQLite as the default datastore stub for the Python SDK. This got me thinking about Django projects using Cloud SQL.
Does anyone know if there are plans to let us use the SQLite datastore with Django’s SQLite backend when working locally? It would be super helpful for development and testing.
I’m curious about how this might affect our workflow and if it could make things easier. Has anyone heard anything about this or tried it out? Any insights would be awesome!
Thanks in advance for your help!
ooh, interesting quesion! i tinkered with django & appengine too. have u seen django-nonrel? its a hack mod for non-relational dbs like gae datastore. im curiious about ur project, are u building something cool? lets chat!
As someone who’s worked extensively with both Django and AppEngine, I can share some insights on this topic. While AppEngine’s switch to SQLite for the local development environment is a step in the right direction, it’s important to note that Django’s SQLite backend and AppEngine’s SQLite datastore are not directly compatible. The main issue lies in the differences between how Django interacts with databases and how AppEngine’s datastore operates. Django expects a traditional relational database, while AppEngine’s datastore, even when using SQLite locally, still adheres to its own unique data model. That being said, for local development, you can use Django with a SQLite database separately from AppEngine’s datastore, which works well for testing and development purposes. However, be mindful of the differences when deploying to production. In my experience, the best approach is to use Django’s ORM with Cloud SQL in production, allowing for a more seamless transition between local development and deployment, albeit with some additional configuration.
hey there! i’ve been messin with appengine n django too. from what i’ve seen, the sqlite backends aren’t exactly the same. appengine’s datastore is kinda its own thing, even with sqlite. for local dev, u can use django with regular sqlite, but it might not match up 100% when u deploy. maybe check out using django with cloud sql instead? that could work better end-to-end.