Uploaded image for project: 'Instrument control development'
  1. Instrument control development
  2. INSTRM-890

Decide on mechanism for saving unsigned integers to SQL.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Normal
    • Resolution: Unresolved
    • Component/s: None
    • Labels:

      Description

      Postgres does not provide unsigned integer types (nor does the SQL standard). At least one of our column types (for pfsDesignIds, etc.) requires 64-bit unsigned ints, which do not have a larger type to upgrade to. Besides that, sqlAlchemy has no existing mechanism for synthesizing a new type.

      There is a pguint extension which people seem to use. Or we could convert signed<->unsigned above the SQL/sqlAlchemy layer. Others? MySQL has unsigned types, FWIW.

      This is not a problem for FITS. For tables, TSCAL and TZERO do the conversion, and for header cards the content of the integer field is (surprisingly) not constrained.

      Kiyoto Yabe? rhl? price?

        Attachments

          Issue Links

          blocks

          Task - A task that needs to be done. INSTRM-1096 Add {{pfs_visit.pfs_design_id}} column

          • Normal - Normal priorities
          • Done

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                cloomis cloomis
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: