Thanks a lot Stan for the overview picture, which is sometimes hard to
acquire by looking at the code.
On this topic, there are a few "constraints" that perhaps should be
considered as Core Zest features somehow, that could make life easier when
insisting on RDBMS backing an Zest application.
On 21.9.2016 12:00, Stanislav Muhametsin wrote:
On 21.9.2016 0:08, Jiri Jetmar wrote:
Independently of that that, things starts to be complicated in the SQL
world with large data when you are submitting e.g. a inner JOIN
statement
in a transactional INSERT expression, where the tables are
On 21.9.2016 0:08, Jiri Jetmar wrote:
Independently of that that, things starts to be complicated in the SQL
world with large data when you are submitting e.g. a inner JOIN statement
in a transactional INSERT expression, where the tables are located (the
data) on different nodes, simply because
On 20.9.2016 2:02, Niclas Hedhman wrote:
Right, but with a single JSON column you have reduced RDBMS to a
KeyValue store. Can the JSON document be indexed in some intelligent
way on Postgres?
Jiri managed to reply to this before me. :)
Isn't the SQL EntityStore already doing this in
