Make returned fields from database api more consistent about spine-database-api HOT 7 CLOSED

In GitLab by @manuelma on Oct 25, 2018, 22:36

But the object function is this one:

db_map.object_parameter_value_list().first()._fields
('id',
 'object_class_name',
 'object_name',
 'parameter_name',
 'index',
 'value',
 'json',
 'expression',
 'time_pattern',
 'time_series_id',
 'stochastic_model_id')

I think it behaves kinda similar to relationship_parameter_value_list.

But the issue is what we use these methods for. Both object_parameter_value_list and relationship_parameter_value_list are tailored to populate the parameter value tables in the treeview.

So if we change them, we also need to change Spine Toolbox. Maybe a better idea (but I'm not sure) is to create new methods for new functionality? Or maybe control what columns are returned via arguments?

from spine-database-api.

In GitLab by @PvPer on Oct 26, 2018, 07:50

I see,

I think the main problem (for me) is that it's not very straightforward to add a column to the queries right now. Specially the wide queries, which seems to blow up a bit when i touch them.

from spine-database-api.

In GitLab by @manuelma on Oct 27, 2018, 15:48

mentioned in commit c7efe86

from spine-database-api.

In GitLab by @manuelma on Oct 27, 2018, 15:49

assigned to @manuelma

from spine-database-api.

In GitLab by @manuelma on Oct 27, 2018, 15:49

See commit c7efe86 with some update on this. Maybe that's enough?

from spine-database-api.

In GitLab by @manuelma on Oct 27, 2018, 16:35

mentioned in commit toolbox@0a26d1e6f996e4b515b4a4b82c7ad6179f322868

from spine-database-api.

Outdated

from spine-database-api.