non-relational-database

问题 I am creating a web site, and the data will be sent in from an external application that has a database full of data, only parts of which are needed for the web site. By "parts" I mean some of the rows in each table, but not all of them. The business in hand is one that manages charity vouchers, and they have customers who have accounts with them. Charities may want to log in to the web site and see info about money paid to them, and customers may want to log in and see info about their

问题 I am creating a web site, and the data will be sent in from an external application that has a database full of data, only parts of which are needed for the web site. By "parts" I mean some of the rows in each table, but not all of them. The business in hand is one that manages charity vouchers, and they have customers who have accounts with them. Charities may want to log in to the web site and see info about money paid to them, and customers may want to log in and see info about their

问题 I'm using mongodb for my python(2.7) project with django framework..when i give python manage.py runserver it will work but if i sync the db (python manage.py syncdb) the following error displayed in terminal Creating tables ... Traceback (most recent call last): File "manage.py", line 14, in <module> execute_manager(settings) File "/usr/lib/pymodules/python2.7/django/core/management/__init__.py", line 438, in execute_manager utility.execute() File "/usr/lib/pymodules/python2.7/django/core

问题 We have different products that rely on relational databases for various reasons, basically the transactional nature of the operations (atomicity, consistency, etc.). This is not going to change any time soon. Given this scenario, are there any possible justifications to export the data to a NoSQL solution? Maybe Datawarehousing, Analytics, etc. Any comments are welcome. 回答1: "Data" is just a vague generality without a data structure. "Relational" means the data structure is relations/tables

问题 BerkeleyDB is the database equivalent of a Ruby hashtable or a Python dictionary except that you can store multiple values for a single key. My question is: If you wanted to store a complex datatype in a storage structure like this, how could you go about it? In a normal relational table, if you want to represent a Person, you create a table with columns of particular data types: Person -id:integer -name:string -age:integer -gender:string When it's written out like this, you can see how a

问题 I'm going to try and make this as straight-forward as I can. Coming from MySQL and thinking in terms of tables, let's use the following example: Let's say that we have a real-estate website and we're displaying a list of houses normally, I'd use the following tables: houses - the real estate asset at hand owners - the owner of the house (one-to-many relationship with houses) agencies - the real-estate broker agency (many-to-many relationship with houses) images - many-to-one relationship with

问题 I'm building a Threaded Messaging System that will be hosted on Google AppEngine I've modeled it after the technique described by Brett Slatkin in Building Scalable, Complex Apps on App Engine class Message(db.Model): sender = db.StringProperty() body = db.TextProperty() class MessageIndex(db.Model): receivers = db.StringListProperty() The issue I'm having to determining the most efficient way to track the message state for a User. For example is a message read , archived , deleted for a

问题 I am in the early stages of developing a sports statistics website (ultimate frisbee) and would like to know your opinions if Google App Engine is right for me. I am writing it in Python using Django and have been comfortable with standard RDBMS for years but this site is a long term project and I am expecting very large amounts of data so I would like the "infinite" scaling that the GAE datastore offers. A vast majority of the queries to the database will return very standard results that

问题 Why should I use document based database like CouchDB instead of using relational database. Are there any typical kinds of applications or domains where the document based database is more suitable than the relational database? 回答1: Probably you shouldn't :-) The second most obvious answer is you should use it if your data isn't relational. This usually manifests itself in having no easy way to describe your data as a set of columns. A good example is a database where you actually store paper

问题 I'm learning traditional Relational Databases (with PostgreSQL) and doing some research I've come across some new types of databases. CouchDB, Drizzle, and Scalaris to name a few, what is going to be the next database technologies to deal with? 回答1: I would say next-gen database , not next-gen SQL. SQL is a language for querying and manipulating relational databases. SQL is dictated by an international standard. While the standard is revised, it seems to always work within the relational