ahachete

44 ms·

391.
by ahachete 11y ago
Not an E/R diagram, but to generate table diagrams that you can navigate (in HTML), SchemaSpy ( http://schemaspy.sourceforge.net/ ) is really good.
392.
by ahachete 11y ago
I thought it was implied in the context, but the "more advanced" obviously meant "more advanced in terms of JSON support". Sorry if there was clarification needed. What SQL Server 2016 will have next year seems to be mor
393.
by ahachete 11y ago
In ToroDB ( https://github.com/torodb/torodb ) we are currently working on implementing MongoDB's oplog server-side. ToroDB would work seamlessly with Meteor, meaning that at the end of the day your data sits on a P
394.
by ahachete 11y ago
I know. But there was no MongoDB bashing -- at least in the comment ;)
395.
by ahachete 11y ago
Surprised by the downvote. It is an open source solution that does exactly what the parent comment was asking (not having to think about how to map json to a relational database). I don't see a problem mentioning some software (again:
396.
by ahachete 11y ago
You could also do it in pg pre 9.4. Just create functional indexes on the paths you wanted to index. The advantage of 9.4 is special indexes for jsonb, which may index the whole field or just some paths. So even pg 9.2 was better than SQLSe
397.
by ahachete 11y ago
Or not ^_^ Have a look at ToroDB ( https://github.com/torodb/torodb ). It is a mongo-compatible database sitting on top of PostgreSQL. You don't need thought, just use it :) Disclaimer: I'm a ToroDB developer
398.
by ahachete 11y ago
Surprised that they mention PostgreSQL. Surprised even more that they seem to admit PostgreSQL is more advanced now than what they are releasing next year. However, they incorrectly mention that PostgreSQL supports BSON. It doesn't. It
399.
by ahachete 12y ago
Also ToroDB ( https://github.com/torodb/torodb ) implements the MongoDB protocol. But it uses PostgreSQL as a backend and it's open source ;P (ToroDB developer here)
400.
by ahachete 12y ago
Have a look at ToroDB ( https://github.com/torodb/torodb ). It's open source, MongoDB-compatible database which uses PostgreSQL to store data. In a relational way (i.e., no jsonb, no blobs). It's still under he
401.
by ahachete 12y ago
That specific MongoDB feature is "tailing the oplog", where the oplog is the capped collection with the idempotent commands that represent the changes in the database. This is what Meteor uses to receive (be pushed) changes (not p
402.
by ahachete 12y ago
Álvaro here from ToroDB. Check out ToroDB (github.com/torodb/torodb). It is a Mongo implementation based on PostgreSQL that transforms JSON documents into relational tables. This has many advantages like significant storage reduct
403.
by ahachete 12y ago
As the post explained, one of the big problems of migration off of MongoDB is finding out the "effective" schema of the data, and then migrating it (according to that schema). By "effective" I mean the resulting structur
404.
by ahachete 12y ago
Or ToroDB ;) https://github.com/torodb/torodb
405.
by ahachete 12y ago
I have commented it above, but have you checked ToroDB? ;) https://github.com/torodb/torodb/
406.
by ahachete 12y ago
There's an open-source implementation of a different approach to the same problem in ToroDB ( http://github.com/torodb/torodb ). ToroDB creates tables dynamically, which match the types (mapped to columns) of every
407.
by ahachete 12y ago
No one is saying that Aurora is built on MySQL, I'd personally like to know :) It's the protocol (drivers) compatibility what has been claimed so far. I'd agree with you from a technical perspective it would have been better
408.
by ahachete 12y ago
For all of you that are not in Spain and want a quick understanding of the situation: it's OK if (some) catalans want to be independent. The fact is that the constitution says that this matter belongs to all Spanish. So if Cataloni
409.
by ahachete 12y ago
Errr yes, you're right, my "yes and yes" was too quick. Sorry for that!
410.
by ahachete 12y ago
Yes and yes :)
411.
by ahachete 12y ago
I'm not saying it's not gonna happen...
412.
by ahachete 12y ago
Indeed. It's more than a JSON to SQL translation, but it could definitely use various backends. It has some plpgsql Postgres code and some data types to speed operations (saving some round trips to the database), but it won't be h
413.
by ahachete 12y ago
platform, very interesting the XMLDB info. As you point out, ToroDB does not require any model declaration ahead. It's perfectly "schema-less", as it 'senses' the model of each document. Regarding ingestion speed, i
414.
by ahachete 12y ago
There is now on the project's wiki ( https://github.com/torodb/torodb/wiki/How-ToroDB-stores-json... ) more detailed information about how ToroDB stores in tables the JSON documents. Hope this information
415.
by ahachete 12y ago
It is true that PostgreSQL has such a high row overhead. But the storage savings are significant, in any way. Please see the presentation pointed out earlier.
416.
by ahachete 12y ago
There are some benchmarks in the following presentation: http://www.slideshare.net/8kdata/toro-db-pgconfeu2014 where ToroDB was presented (PostgreSQL Europe Conference, Madrid, 2014, 2014.pgconf.eu).
417.
by ahachete 12y ago
Data is laid out transparently to the user. Indeed, there should be no (visible) difference as to how it is stored. Data within a single "level" is stored on a single table. If you want to keep blobs, you can definitely do that, t
418.
by ahachete 12y ago
Thanks! Documents are split into chunks before hitting the database, so there is no need to reconstruct trees in PostgreSQL. Indeed, many queries don't need to reconstruct the (whole) tree, just a part of it or even just one level. How
419.
by ahachete 12y ago
zrail, it's difficult to find the schema and/or tables in the source code as all of them are 100% dynamic. See my coments above about the internal workings of ToroDB. Or give it a try, run it and check how data is laid out! Regard
420.
by ahachete 12y ago
ToroDB is definitely going to have MongoDB's oplog, so it should work as is for live-updating. SQL support for ToroDB... there's surely room for it in the future ;)

More ›