Ticket #880 (closed defect: fixed)

Opened 2 years ago

Last modified 16 months ago

MS SQL identity colums not detected correctly

Reported by: zomg Owned by: jwage
Priority: minor Milestone: 1.0.4
Component: Import/Export Version: 1.0.2
Severity: Keywords: mssql
Cc: Has Test: no
Status: Pending Core Response Has Patch: no

Description

MS SQL Server IDENTITY column attribute does not get detected properly. If it's IDENTITY(1, 1) it should be detected as an auto increment column. This happens at least when generating YAML from the database. This breaks at least saving related records.

Change History

Changed 2 years ago by zomg

  • owner changed from somebody to lsmith
  • component changed from general to Import/Export

Changed 23 months ago by jwage

  • version changed from 0.10 to 0.11
  • milestone changed from 0.11.0 to 0.11.1

Changed 20 months ago by romanb

  • has_patch unset
  • milestone changed from 0.11.1 to 1.0.0-BETA1
  • mystatus set to Pending Core Response
  • has_test unset

Changed 20 months ago by lsmith

  • owner changed from lsmith to jwage

Changed 19 months ago by jwage

  • version changed from 0.11 to 1.0
  • milestone changed from Unknown to 1.0.0-RC2

Changed 18 months ago by anonymous

  • milestone New deleted

Milestone New deleted

Changed 18 months ago by jwage

  • version changed from 1.0.0 to 1.0.2
  • milestone set to 1.0.4

Changed 16 months ago by guilhermeblanco

  • status changed from new to closed
  • resolution set to fixed

(In [5210]) [1.0, 1.1] fixes #880. MSSQL Identity columns are not generated as autoincrement: true when generating yaml from db.

Note: See TracTickets for help on using tickets.