-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SmartGCal support for Flamingos2 #1573
Conversation
|
||
object Flamingos2: | ||
|
||
case class SearchKey( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is taken from Gmos, I'm not sure if I need a separate SearchKey
and TableKey
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm struggling to remember why I thought I needed distinct types for GMOS. It may be that the search key once separated the wavelength. I'm not sure. If you don't see a need for the distinction by all means merge them.
PRIMARY KEY (c_instrument, c_gcal_id), | ||
|
||
FOREIGN KEY (c_instrument, c_gcal_id) REFERENCES t_gcal(c_instrument, c_gcal_id), | ||
CONSTRAINT check_is_gmos_south CHECK (c_instrument = 'Flamingos2'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check_is_f2
We'll need to update the |
14cf165
to
6d1971c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, as far as I can tell.
This is for review I still need to do a core release before merging.
@swalker2m This is what I found was needed for SmartGCal but maybe I'm missing something else?