News for hackers. Stuff that matters.
Re:Why You Should Never Use MongoDB by tensor on Monday November 11, 2013 @07:18PM (#6715039)
Of course, a better choice now would be to use PostgreSQL's new JSON support. Postgres has also had XML document types for a long time, though I'm not sure of their indexing story.

If you don't need indexing into the document, you can easily just store it as serialized bytea data. I've done this quite frequently and it works wonderfully.

Re:Why You Should Never Use MongoDB by threeseed on Monday November 11, 2013 @07:51PM (#6715160)
Sorry but PostgreSQL's JSON query syntax is insanely complicated compared to MongoDB.

And that is a big deal for a lot of developers.

Re:Why You Should Never Use MongoDB by tensor on Monday November 11, 2013 @08:07PM (#6715216)
I just took a look, and if I'm getting this right, it looks about as simple as it gets:

SELECT json_data FROM people WHERE json_data->'age' > 15

vs

db.people.find( { age: { $gt: 10 } } )

Personally, I prefer the postgres syntax. It's much clearer. I also don't buy your claims below about performance. Can you provide a real benchmark? Are you running with the safeties off meaning you lose data?

Re:Why You Should Never Use MongoDB by dbcfd on Monday November 11, 2013 @09:00PM (#6715392)
What is the syntax on finding an array value matching some key? E.g. given a user with field "favFoods":[String], how do I determine that pizza is in there?
Re:Why You Should Never Use MongoDB by jessedhillon on Monday November 11, 2013 @10:14PM (#6715627)
select ... where "pizza" in person -> favFoods
Re:Why You Should Never Use MongoDB by jessedhillon on Tuesday November 12, 2013 @03:29AM (#6716501)
Sorry I'm stupid, I was thinking Python

select ... where person -> favFood in ("pizza")

Re:Why You Should Never Use MongoDB by gfodor on Tuesday November 12, 2013 @01:59AM (#6716289)
Your ORM will give you whatever syntax is natural, eventually.