In the beginning I thought about making an api which supports column
databases such as cassendra but would mean that i would need to first find
commonalities between all 3 ( column , document and relational ) but such
commonalities would be lesser and so finally i would require to create a
There are two goals when it comes to document DB support. First goal
is to allow usage of models written specifically for document oriented
databases. This is something that should be possible to achieve even
if there are some hard problems to solve. The other goal is to allow
usage of any Django
It would also be worthwhile looking into the prior art on this topic. We
had a GSoC project for non-relational data stores a few years back, and
came to the conclusion that it probably wasn’t viable. You can dig into the
archives to find out why.
If you’re interested in adding non-relational
It sounds like by "NoSQL DBS" you mean specifically "Document store
DBMS". Is this correct?
(I'm sure most people know my rant about how "NoSQL" is a misnomer, and
it's really "Non-relational" that people mean - it's not SQL per se
they're avoiding, it's the relational model)
The
Hello,
I would like to propose providing a standard interface for NoSQL databases
. Some the points to consider are:
1. The *Fields *which are used to define the schema of the sql databases
can also be used to provide in No sql databases.
2. In NoSQL dbs ,developers usually store
