rdbms

I have a NoSQL system for storing real estate houses. One piece of information I have in my key-value store for each house is the longitude and latitude . If I wanted to retrieve all houses within a geo-lat/long box, like the SQL below: SELECT * from houses WHERE latitude IS BETWEEN xxx AND yyy AND longitude IS BETWEEN www AND zzz Question: How would I do this type of retrieval with NoSQL ... using just a key-value store system? Even if I could do this with NoSQL, would it even be efficient or would simply going back to using a tradition database retrieve this type of information faster? Sql

I've volunteered with a Non-Governmental Organization to help with their record-keeping at their community centre. At present, there is only one community centre where all their data is stored. However, this is expected to change by the end of the year. Presently their data is maintained using a workbook with two sheets. Each record in the main sheet may have upto 100 follow-ups in the follow-up sheet. Data is loosely structured, and there are no explicit constraints. Moving all existing data from a spreadsheet to an RDBMS would require effort, but I'm willing to do that; particularly since

How can I store logical expressions using a RDBMS? I tag objects and would like to be able to build truth statements based on those tags. (These might be considered as virtual tags.) Tags new for_sale used offer Rule second_hand_goods = (!new or used) and for_sale new_offer = new and offer second_hand_offer = second_hand_goods and offer Rules should be able to reference both tags and other rules. Schemas that can be easily accessed by hibernate would be preferrable. Preferably it will be possible to retrieve the entire rule in one select/call? How do you guys store expressions and business

Simple question, could I conceivably use redis instead of mysql for all sorts of web applications: social networks, geo-location services etc? Nothing is impossible in IT. But some things might get extremely complicated. Using key-value storage for things like full-text search might be extremely painfull. Also, as far as I see, it lack support for large, clustered databases: so on MySQL you have no problems if you grow over 100s of Gb in Database, and on Redis... Well, it will require more effort :-) So use it for what it was developed for, storing simple things which just need to be retreived

Coming from question “Relation” versus “relationship” What are definitions of "relation" vs. "relationship" in RDBMS (or database theory)? Update: I was somewhat perplexed by comment to my question: "relation is a synonym for table, and thus has a very precise meaning in terms of the schema stored in the computer" Update2: Had I answered incorrectly that question , in terms of RDBMS, having written that relation is one-side direction singular connection-dependence-link, i.e. from one table to another while relationship implies (not necessarily explicitly) more than one link connection in one

I have to store scheduled events, (like say class times, for example) that can be organized on a weekly, daily or monthly basis. Events can occur, say, every Monday and Wednesday, or every second Thursday of the month. Is there a way to store this information in an RDBMS that adheres to 3NF? EDIT: This is not homework; I'm building something with a friend for our own edification and we want it in 3NF. To be specific, I'm trying to store the schedules for mass and confession times at RC parishes. These can be scheduled in a hell of a lot of ways, such as every Sunday at x time or every Tue/Thu