Some example queries are:
give me all attributes for entity1 where entity1.attribute1 > 1000 and
entity1.attribute15 = "someValue"
give me all attributes for entity1 where entity1.parentId = 1
give me all attributes for entity1 & parent_entity where entity1.attribute2
= "this"
Nothing too com
Op 14/04/2017 om 19:03 schreef Rj Ewing:
We do know where we want to end up. We've had the application running
for a while using a triple store db. We're looking to move away from
the triple store due to performance issues. Our core concept is that
each project can define a set of entities and
We do know where we want to end up. We've had the application running for a
while using a triple store db. We're looking to move away from the triple
store due to performance issues. Our core concept is that each project can
define a set of entities and their relations. Each entity has a set of
att
On Tue, Apr 11, 2017 at 12:46 PM, Rj Ewing wrote:
> I'm looking for thoughts on the best way to handle dynamic schemas.
>
> The application I am developing revolves around user defined entities. Each
> entity is a tabular dataset with user defined columns and data types.
> Entities can also be rel
I've done the dynamic-table-per-project previously and it worked great.
Even dynamic indexes on it. If low thousands it should work ok. If more
than that, use as many static-columns as possible, everything dynamic in
jsonb, and check stuff with per-project-constraints.
On Wed, Apr 12, 2017 at 3:31
I thought that might be an answer around here :)
I guess I was looking for what might be a better approach.
Is dynamically creating a table for each entity a bad idea? I can see something
like creating a schema for each project (group of related entities) and then
creating a table for each sch
Poul,
I took a quick look at the demo site, but didn't see anything where the user
was defining the fields. It looks like they can choose from a list of
predetermined metadata fields. Looking at the code, but not actually seeing the
total db schema, it looks like they might be using the EAV pat
If you are asking if you should go nosql, 99% you should not.
On Tue, Apr 11, 2017 at 10:06 PM, Poul Kristensen wrote:
> dataverse.org uses Postgresql and is well documented + it is completely
> user driven. Maybe the concept could be usefull for you. I have installed
> and configuration a few t
dataverse.org uses Postgresql and is well documented + it is completely
user driven. Maybe the concept could be usefull for you. I have installed
and configuration a few to be uses for researchers.
regards
Poul
2017-04-11 19:46 GMT+02:00 Rj Ewing :
> I'm looking for thoughts on the best way to
I'm looking for thoughts on the best way to handle dynamic schemas.
The application I am developing revolves around user defined entities. Each
entity is a tabular dataset with user defined columns and data types.
Entities can also be related to each other through Parent-Child
relationships. Some
10 matches
Mail list logo