It depends what you need, We use redis for non sql, and postgres for sql, You can use an id field to have a link between them.
Django 1.8 has a support for postgres specific fields like HStore, maybe this is good enough for you? Galia On Tuesday, May 19, 2015 at 2:40:17 AM UTC+2, Roger Dunn wrote: > > I'm spinning up a new project and nearly all of the data I need to store > can be normalized. Along with this normalized data is one piece that is > better suited to a nosql database. > > The use case is that the normalized data will be fetched often, is very > tabular in nature, and the additional data is more document centric and > will be fetch less often, by quite a margin. > > I'm thinking of doing a hybrid using the 2 technologies. There will be a 1 > for 1 relationship by rows. I know I could do either nosql or mysql, but > for the exercise thinking of doing both. > > Any examples floating around for this? > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a77b0e65-2ace-417c-a555-a199fd6c7c20%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
