View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004531 | SymmetricDS | Bug | public | 2020-09-09 14:48 | 2020-09-23 20:34 |
Reporter | pmarzullo | Assigned To | pmarzullo | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.10.12 | ||||
Target Version | 3.12.4 | Fixed in Version | 3.12.4 | ||
Summary | 0004531: Postgres Varchar column with no defined length getting converted to a LONGVARCHAR | ||||
Description | When a Varchar type column (character varying) in Postgres is specified without a length, the column type gets changed into a LONGVARCHAR as the mapped type code. When this column is the primary key, then it is thrown away as the use as primary key because we don't support LONGVARCHAR or LONGVARBINARY types as primary keys, and then all columns are used as the primary key. The changing of the VARCHAR mapped type code should only be changed to LONGVARCHAR when the original column type is TEXT. | ||||
Tags | dialect: postgresql | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2020-09-09 14:48 | pmarzullo | New Issue | |
2020-09-09 14:48 | pmarzullo | Status | new => assigned |
2020-09-09 14:48 | pmarzullo | Assigned To | => pmarzullo |
2020-09-09 14:48 | pmarzullo | Tag Attached: dialect: postgresql | |
2020-09-09 14:49 | pmarzullo | Relationship added | related to 0004529 |
2020-09-09 14:49 | pmarzullo | Relationship added | related to 0004530 |
2020-09-09 16:23 | pmarzullo | Status | assigned => resolved |
2020-09-09 16:23 | pmarzullo | Resolution | open => fixed |
2020-09-09 16:23 | pmarzullo | Fixed in Version | => 3.12.4 |
2020-09-23 20:34 | admin | Status | resolved => closed |