Insertion error in fresh database

[samuelbray32]

• When populating LinearizedPositionV1 for the first time in a database, I got an error that cannot call make within a transaction.
• I think what happened is that the "position_linearization_merge" schema had not yet been made, and it tried to do so at this point

spyglass/src/spyglass/linearization/v1/main.py

Line 180 in 10bf4ac

LinearizedPositionOutput._merge_insert(

• This left the database in a state whereLinearizedPositionV1 was populated for the entry, but the corresponding part table in PositionOutput was not.

Solution
@CBroz1 Is there a preferred way to ensure that the LinearizedPositionOutput table is constructed before this step?

[CBroz1]

I think this is a symptom of the norm we've established whereby populates insert into downstream tables, which I would advise against.

In the long term, I'd like to see us move to a norm of running MergeTable.merge_populate('UpstreamTable', mykey) to conduct this set of populate/merge_insert actions.

In the short term, this populate could check the _is_declared property before running calculations and error out if not, asking the user to import the downstream table

[samuelbray32]

@CBroz1
I might be missing something, but it looks like datajoint changed that property to is_declared

But to access the property, you have to make an instance of the table, which would declare it in the database. This:

1. means the property is always true
2. Would raise the error above in the process anyways.

Am I understanding this wrong, or should it be a staticmethod or classmethod in datajoint