▸case-01 We just discovered a defect during our database migration where sequence generation behaves differently in PostgreSQL compared to Oracle. In bulk inserts for `OrderRepository.cs`, key collisions occur because of sequence caching differences. Could you draft a complete migration bug report for this issue, including the problem description, reproduction steps, root cause, proposed fix, and validation actions? | fail→pass | 16,187 | 13,504 | -17% | 1 | 1 | 0% | 2,825 | 2,866 | +1% | 0 | 0 | — |
▸case-02 During our migration from Oracle to PostgreSQL, our reporting component `FinancialReportService` started returning wrong row counts. Oracle treats empty string query parameters as NULL in the WHERE clause, while Postgres treats them as literal empty strings, failing automated test `TestMonthlyReconciliation`. Please write a structured bug report documenting this behavioral discrepancy, technical root cause, and resolution. | fail→pass | 12,179 | 7,828 | -36% | 1 | 1 | 0% | 2,364 | 2,098 | -11% | 0 | 0 | — |
▸case-03 I need a formal bug report created for our payment processing service (`PaymentGateway.Core`). In Oracle, a SYS_REFCURSOR automatically handled numeric type conversions, but in Postgres, strict type coercion triggers a casting exception in `ProcessPayout()`. Please generate the bug report file detailing the issue, reproduction scenario, fix details, and database validation steps. | fail→pass | 14,930 | 10,592 | -29% | 1 | 1 | 0% | 3,020 | 2,801 | -7% | 0 | 0 | — |
▸case-04 Our team is migrating the customer database from Oracle 19c to PostgreSQL 15. We need an SQL DDL script to convert our Oracle `CUSTOMER_MASTER` table definition (including VARCHAR2, NUMBER, and DATE types) to PostgreSQL CREATE TABLE syntax. Please provide the PostgreSQL DDL script for creating this table. | pass→pass | 12,001 | 8,525 | -29% | 1 | 1 | 0% | 2,576 | 2,389 | -7% | 0 | 0 | — |
▸case-05 Users report that the user profile dropdown menu in our React Web UI (`UserProfileMenu.tsx`) fails to close when clicking outside the menu element on iOS Safari browsers. Please draft a standard Jira bug report for our frontend team to fix this UI interaction bug. | pass→pass | 8,588 | 9,351 | +9% | 1 | 1 | 0% | 1,567 | 2,364 | +51% | 0 | 0 | — |
▸case-06 We are evaluating whether to use AWS Aurora PostgreSQL or managed Azure Database for PostgreSQL for our database migration architecture. Please draft an Architecture Decision Record (ADR) detailing the key decision criteria, trade-offs, and infrastructure considerations for choosing our target cloud database provider. | pass→pass | 21,531 | 17,203 | -20% | 1 | 1 | 0% | 3,770 | 3,401 | -10% | 0 | 0 | — |
▸case-07 We noticed a bug in `InventoryService.cs` (in project `SupplyChain.Inventory`) where string padding on fixed-length CHAR columns causes string comparison failures in PostgreSQL. In Oracle, CHAR comparison auto-trimmed trailing spaces, but PostgreSQL strict CHAR padding breaks query matching. Please draft the migration bug report, saved with the required project filename path convention. | fail→pass | 13,153 | 10,374 | -21% | 1 | 1 | 0% | 2,556 | 2,405 | -6% | 0 | 0 | — |
▸case-08 Our `CustomerPortal.Api` application failed test `TestTimestampTimezoneConversion` during migration. Oracle implicitly handled TIMESTAMP WITH TIME ZONE conversions using session timezones, whereas PostgreSQL TIMESTAMP WITHOUT TIME ZONE discarded offset data, causing UTC drift in `AuditLogRepository.cs`. Create a migration defect report for this issue. | fail→pass | 12,720 | 8,570 | -33% | 1 | 1 | 0% | 2,377 | 2,101 | -12% | 0 | 0 | — |
▸case-09 During migration of `BillingEngine.Core`, stored procedure `CalculateMonthlyTax` threw an error because PostgreSQL sequence `.NEXTVAL` syntax differs from Oracle's `SEQUENCE.NEXTVAL`. Automated test `TestTaxCalculationSequence` failed. Draft a defect report following standard migration bug reporting format. | fail→pass | 9,468 | 8,694 | -8% | 1 | 1 | 0% | 2,037 | 2,216 | +9% | 0 | 0 | — |
▸case-10 In our project `OrderProcessing.Service`, constraint checking in PostgreSQL raises immediate exceptions during statement execution, while Oracle deferred constraint checking until transaction commit in procedure `ProcessOrderBatch`. Automated test `TestBatchOrderCommit` failed. Draft a migration bug report. | fail→pass | 11,326 | 7,933 | -30% | 1 | 1 | 0% | 2,199 | 1,924 | -13% | 0 | 0 | — |
▸case-11 We encountered a defect in `UserManagement.Identity` where NULL sorting order broke pagination. Oracle puts NULLs last in ascending order by default, whereas PostgreSQL puts NULLs first, breaking test `TestUserListPagination`. Write a complete bug report for this issue. | fail→pass | 11,023 | 9,402 | -15% | 1 | 1 | 0% | 2,209 | 2,570 | +16% | 0 | 0 | — |
▸case-12 In `AnalyticsService.Engine`, a migration defect occurred because Oracle implicit string-to-date conversion (`TO_DATE('2023-05-01')`) worked without explicit format masks, whereas PostgreSQL strictly rejected implicit date coercions in `FetchAnalyticsData()`. Automated test `TestDateCoercion` failed. Write the migration defect report. | fail→pass | 11,041 | 10,009 | -9% | 1 | 1 | 0% | 2,312 | 2,469 | +7% | 0 | 0 | — |
▸case-13 While migrating stored procedure `UpdateAccountBalance` in `CoreBanking.Services`, implicit cursor loop variables behaved differently under error handling, causing test `TestAccountBalanceRollback` to fail. Draft the migration defect report. | fail→pass | 14,661 | 12,210 | -17% | 1 | 1 | 0% | 2,527 | 2,707 | +7% | 0 | 0 | — |
▸case-14 In `NotificationService.Worker`, string concatenation with NULL values produced different results: Oracle treats `NULL || 'Text'` as `'Text'`, while PostgreSQL treats `NULL || 'Text'` as `NULL`, breaking test `TestTemplateFormatting`. Produce the migration bug report. | fail→pass | 9,735 | 8,395 | -14% | 1 | 1 | 0% | 1,842 | 2,167 | +18% | 0 | 0 | — |
▸case-15 We found that default column value evaluations for UUID/RAW types in `SecurityModule.Auth` differ: Oracle RAW(16) GUID generation vs PostgreSQL `gen_random_uuid()`. Test `TestUserTokenGeneration` failed. Generate a bug report detailing this defect. | fail→pass | 13,241 | 11,530 | -13% | 1 | 1 | 0% | 2,469 | 2,785 | +13% | 0 | 0 | — |
▸case-16 In `PayrollEngine.Calculator`, numeric division precision differs when operating on DECIMAL types, causing fractional penny rounding errors in test `TestSalaryCalculation`. Draft a formal migration defect report. | fail→pass | 13,001 | 9,791 | -25% | 1 | 1 | 0% | 2,186 | 2,136 | -2% | 0 | 0 | — |
▸case-17 When querying `LOG_ENTRIES` in `LoggingService.DataAccess`, Oracle case-insensitivity on unquoted identifiers caused no issue, but PostgreSQL lowercase folding caused relation `LOG_ENTRIES` not found errors, breaking test `TestLogFetch`. Generate the defect report. | fail→fail | 10,741 | 8,922 | -17% | 1 | 1 | 0% | 2,024 | 2,152 | +6% | 0 | 0 | — |
▸case-18 In `CatalogService.Search`, wildcards in LIKE queries handled trailing whitespace differently between Oracle and PostgreSQL, failing test `TestCatalogProductSearch`. Write a bug report for this issue. | fail→pass | 9,873 | 11,103 | +12% | 1 | 1 | 0% | 1,763 | 2,467 | +40% | 0 | 0 | — |
▸case-19 In `FreightModule.Shipping`, Oracle `VARCHAR2` size limits (in bytes vs characters) caused string truncation errors when inserting UTF-8 strings into PostgreSQL `VARCHAR` columns during test `TestInternationalAddressSave`. Create a migration defect document. | fail→pass | 20,049 | 15,896 | -21% | 1 | 1 | 0% | 3,447 | 3,167 | -8% | 0 | 0 | — |
▸case-20 In `DocumentManagement.Storage`, BLOB handling via Oracle `EMPTY_BLOB()` failed in PostgreSQL bytea mappings during automated test `TestDocumentUpload`. Draft the migration bug report. | fail→fail | 11,431 | 10,126 | -11% | 1 | 1 | 0% | 2,094 | 2,188 | +4% | 0 | 0 | — |
▸case-21 In `TelemetryEngine.Collector`, partition pruning queries using `INTERVAL` arithmetic failed on PostgreSQL due to syntax differences with Oracle date math, failing test `TestPartitionPruning`. Create a migration defect report. | fail→pass | 12,211 | 9,834 | -19% | 1 | 1 | 0% | 2,225 | 2,304 | +4% | 0 | 0 | — |
▸case-22 In `ClaimProcessing.Rules`, Oracle's `DECODE` function was replaced by CASE expressions in PostgreSQL, but unexpected NULL handling in complex expressions broke test `TestClaimRuleEvaluation`. Write the migration bug report file. | fail→pass | 13,207 | 10,358 | -22% | 1 | 1 | 0% | 2,459 | 2,504 | +2% | 0 | 0 | — |