Issues

Select view

Select search mode

 
50 of 428

Sunflower 2025-R1 Schema testing

Done

Environment

None

Potential Workaround

None

Attachments

6
  • 11 Mar 2025, 11:00 AM
  • 11 Mar 2025, 10:40 AM
  • 11 Mar 2025, 10:35 AM
  • 11 Mar 2025, 10:25 AM
  • 11 Mar 2025, 10:13 AM
  • 11 Mar 2025, 10:09 AM

Checklist

hide

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Thunderjet

Release

Not For Release

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 7, 2025 at 9:40 AM
Updated March 11, 2025 at 1:23 PM
Resolved March 11, 2025 at 1:23 PM

Activity

Show:

Serhii_Nosko March 11, 2025 at 1:23 PM

We agreed that this is expected discrepancy because we use CREATE TABLE IF NOT EXISTS and had in subsequent PR modified it, and change was not applied because table already exist. This is not a case for Bugfest and production envs, so we are good here.

Boburbek Kadirkhodjaev March 11, 2025 at 11:01 AM

Found 1 minor discrepancy in the job_number table schema, but other than that all is good

Boburbek Kadirkhodjaev March 11, 2025 at 10:44 AM
Edited

https://github.com/folio-org/mod-finance-storage/pull/463

  • Applied DB changes src/main/resources/templates/db_scripts/schema.json

Updated the default value on job_number table from 1 to 0

But found a discrepancy between the expected and actual schema states, although it is probably due to the absence of an alter query in the PR which should’ve updated the existing table with the new field default value

image-20250311-105958.png

Boburbek Kadirkhodjaev March 11, 2025 at 10:42 AM

Boburbek Kadirkhodjaev March 11, 2025 at 10:42 AM

TestRail: Cases
TestRail: Runs

Flag notifications