/prog/ - YesSql vs NoSql

Name: Anonymous 2013-02-25 22:25

Which one should I use?

Name: Anonymous 2013-02-26 1:17

fuck you faggot, now hax my anus

Name: Anonymous 2013-02-26 3:59

>>1
Yes, SQL. PostgreSQL, or Berkeley_DB or SQLite for lite stuff. Reqex is always necessary. Also, requirements might be awesome to have, to give you the best solution.

Name: Anonymous 2013-02-26 4:04

Reqex

REQEX Mutual Fund

Name: Anonymous 2013-02-26 4:06

>>4
lol, oops. s/reqex/regex/

Name: Anonymous 2013-02-26 4:55

Use textfiles and regular expressions.

Name: Anonymous 2013-02-26 4:57

NoSQL a shit

Name: Anonymous 2013-02-26 4:57

Except for unreliable non-critical simple data, NoSQL is not even a choice.

Name: Anonymous 2013-02-26 11:10

Let's assume you're going to need something more complex than simple key/value pairs. Are you really going to design your program around the database? Are you going to follow the software life cycle - consider all the data you need, put it in third normal form, and then not touch the format once you've started implementation?
I didn't think so. Don't use SQL.

Name: Anonymous 2013-02-26 13:57

>>9
what is CREATE TABLE

Name: Anonymous 2013-02-26 13:59

>>10
what is Adding new tables is useless if the existing data format is shitty.

Name: Anonymous 2013-02-26 15:39

>>11
what is ALTER TABLE

Name: Anonymous 2013-02-26 15:44

>>12
what is Enjoy rewriting most of your program logic and introducing bugs.
Do you usually have conversations in such painfully small increments?

Name: Anonymous 2013-02-26 22:57

>>9,11,13
I am still waiting for your ACID compliant struct that you use for quick manipulation of data when programs change on the fly.

Name: Anonymous 2013-02-27 4:24

>>13
I don't see how anything else will help there, with the schema-less NoSQL databases you'll need to refactor everywhere anyway to handle the new format and support every iteration of the old format as well.

Name: Anonymous 2013-02-27 7:24

>>14
I haven't written one. But at least with a struct, all errors introduced by changing something will be caught at compile-time.

>>15
It's a trade-off between apparent type-safety and convenience. Compare a struct with a hashtable, for instance. The new format introduced won't change anything because the existing codebase could not make any assumptions about the structure of the nosql database in the first place.

Name: >>3,5,14 !/taFYe4zuk!WU4EDkKiqHjIcWY 2013-02-27 8:49

>>16
read carefully what you just posted. Ponder in it, and test it with a mental exercise.

Then after you have done so, we can discuss.

YesSql vs NoSql

1 Name: Anonymous 2013-02-25 22:25

2 Name: Anonymous 2013-02-26 1:17

3 Name: Anonymous 2013-02-26 3:59

4 Name: Anonymous 2013-02-26 4:04

5 Name: Anonymous 2013-02-26 4:06

6 Name: Anonymous 2013-02-26 4:55

7 Name: Anonymous 2013-02-26 4:57

8 Name: Anonymous 2013-02-26 4:57

9 Name: Anonymous 2013-02-26 11:10

10 Name: Anonymous 2013-02-26 13:57

11 Name: Anonymous 2013-02-26 13:59

12 Name: Anonymous 2013-02-26 15:39

13 Name: Anonymous 2013-02-26 15:44

14 Name: Anonymous 2013-02-26 22:57

15 Name: Anonymous 2013-02-27 4:24

16 Name: Anonymous 2013-02-27 7:24

17 Name: >>3,5,14 !/taFYe4zuk!WU4EDkKiqHjIcWY 2013-02-27 8:49

Name: Anonymous 2013-02-25 22:25

Name: Anonymous 2013-02-26 1:17

Name: Anonymous 2013-02-26 3:59

Name: Anonymous 2013-02-26 4:04

Name: Anonymous 2013-02-26 4:06

Name: Anonymous 2013-02-26 4:55

Name: Anonymous 2013-02-26 4:57

Name: Anonymous 2013-02-26 4:57

Name: Anonymous 2013-02-26 11:10

Name: Anonymous 2013-02-26 13:57

Name: Anonymous 2013-02-26 13:59

Name: Anonymous 2013-02-26 15:39

Name: Anonymous 2013-02-26 15:44

Name: Anonymous 2013-02-26 22:57

Name: Anonymous 2013-02-27 4:24

Name: Anonymous 2013-02-27 7:24

Name: >>3,5,14 !/taFYe4zuk!WU4EDkKiqHjIcWY 2013-02-27 8:49