Unless you have a specific need of a NoSQL feature the fact that you
have many related tables seems a better use case for SQL relational
database.
Enjoy,
Alex
On 05/30/2013 08:42 AM, Avraham Serour wrote:
can't see the image properly, too small, clicking on larger doesn't load
and the expand button on the right bottom corner doesn't work
On Thu, May 30, 2013 at 5:42 PM, Hélio Miranda <helio...@gmail.com> wrote:
Good!
Not sure this is the most appropriate place to put it, if not I apologize.
My question is as follows:
I have to implement a scheme about football, all data on clubs, players
and games as their statistics.
The doubt I have is whether it is more advisable to do it in SQL or NoSQL
as I was asked to do and if you can do in NoSQL. Because it has several
relationships and joins, and joins NoSQL will not.
My scheme is this:
http://www.4shared.com/folder/h_k3P6KE/_online.html
Someone can give me a hint about this?
It is feasible to do in NoSQL, or the best is even in SQL?
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
