Dynamic database schema with and without Django ORM
I work in a company that engaged in the development of the web-based RAMD (Rapid Mobile Application Development) software.
Our product provides an easy way to transform external data sources (such as ODBC, SAP, etc) to the API for mobile applications.
We try to develop tools to create mobile applications that will be convenient to use without thinking about how it works. This is a promising area of software development.
To solve that goal, we have to store and process large amounts of tabular data with structure unknown in advance. This forces us to use dynamic data schemes, but Django ORM were not designed for that case.
We tried to use a variety of ready-made solutions, developed a django model factory and used "raw" the SQL queries.
In this presentation I am going to share the experience of usage dynamic models, to consider ways to address the problems and describe encountered pitfalls.
In my statement, I will try to focus on some aspects ready-made solutions and the Django ORM in particular. Whether to use Django ORM or raw SQL instead.
Russia. Saint Petersburg
My name is Ivan Larin, and I am a senior software engeneer. I am originally from Novosibirsk, though I currently live in Saint Petersburg.
I've liked Python since I first used it over 9 years ago.
Since beginning my programming career in 2012, I have make commercial systems for clients from Eastern Europe, and The United States and Russia of course.