arch-kiosk / arch-kiosk-office

💼 central place for collaboration
GNU Affero General Public License v3.0
1 stars 0 forks source link

add tz fields to dsd automatically #2786

Open urapadmin opened 1 month ago

urapadmin commented 1 month ago
  • we need to store the time zone information separately. Kiosk automatically creates a tz field for every TIMESTAMPTZ field. So the field “created” automatically gets a “created_tz” field. It is not explicitly mentioned in the DSD but Kiosk adds it automatically to the DSD.
  • This field is not listed in the DSD file, it is automatically managed by Kiosk for every TIMESTAMP field that exists:
    
    created: [datatype(TIMESTAMP), replfield_created()]
    modified: [datatype(TIMESTAMP), replfield_modified()]

    looks in future like this (when kiosk code deals with the dsd):

    created: [datatype(TIMESTAMP), replfield_created()]
    created_tz: [datatype(TZ)]
    modified: [datatype(TIMESTAMP), replfield_modified()]
    modified_tz: [datatype(TZ)]
  • urapadmin commented 1 month ago
    • see also #2785
    urapadmin commented 1 month ago
    • [X] the whole migration sub system needs to be mapped and modelled before I can change it. I wrote that too long ago.
    urapadmin commented 1 month ago

    this is implemented. The tz fields are added to the raw dsd structure is read from a file or comes in through .append. They are added BEFORE the new structure is included in the current DSD fields. So that's as early as possible, For now I am trying it with the new datatype "TZ".