Skip to content

Conversation

@stufisher
Copy link
Contributor

@stufisher stufisher commented Jun 28, 2022

We would like to store one or more Positioners with a BLSampleImage, primary to define the z motor position so that rois/pois can be bought back into focus from a sample image where there is no online axis camera.

This table will work both with and without #105 (i'm not ready to deploy the changes in #105 yet at ESRF)

@stufisher stufisher changed the title add sampleimage positioners Add sampleimage positioners Jun 28, 2022
Copy link
Member

@KarlLevik KarlLevik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could do with a table comment to explain what the table is for.

RESTRICT is the default for both ON DELETE and ON UPDATE. This is what you want for both FKs?

Copy link
Member

@KarlLevik KarlLevik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is much of a case for charset + collation as utf8mb4 on this table. Would prefer if it just used the database default. Also not sure we should specify the storage engine. We do of course specify it in the tables.sql, but maybe that is a mistake. It makes it harder to migrate to another storage engine, or for a facility to choose a different storage engine should they wish to do that. InnoDB is the default anyway.

@stufisher stufisher force-pushed the sampleimage_positioner branch from c1e0a3a to 2869ee9 Compare August 17, 2022 10:00
@stufisher stufisher force-pushed the sampleimage_positioner branch from 2869ee9 to f52e881 Compare August 18, 2022 10:16
@KarlLevik KarlLevik merged commit 3c6b050 into DiamondLightSource:master Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants