Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Minor |
| Complexity | Unknown |
| Component | Tools - Table Data Editor |
| Version | 19.0 |
Investigate supporting complex datatypes for PostgreSQL
See AFTableColumnInitPostgreSQL. End of file has list of complex data types. We currently have them disabled for editing. We can try enabling and testing to see if the String type is sufficient to make it work. e.g. :
postgresqlList.put("MACADDR", new AFTableColumnInfo(String.class, AFTableColumnInfo.STRING, false, java.sql.Types.VARCHAR, String.class));
|
|
126 KB
|
|
77 KB
|
|
75 KB
|
|
551 KB
|
|
63 KB
Turned on editing AFTableColumnInitPostgreSQL for the following:
Batch import is working. See here.
Arrays are scripted and displayed correctly. See here.
TDE still does not work if the primary key is one of these types. Will maybe have to put in a fix similar to svn#54948 so that the predicate does a text search when doing an update.
UPDATE "public"."some_datatypes1" SET "col1_bytea"='123456' WHERE CAST("col1_polygon" AS TEXT) = '((2,3),(12,23))'
This does work with primitive datatypes.
UPDATE "public"."some_datatypes1" SET "col1_bytea"='313233343536' WHERE col1_integer = 123456
Need more investigation with TDE.
Batch import is working. See here.
Arrays are scripted and displayed correctly. See here.
TDE still does not work if the primary key is one of these types. Will maybe have to put in a fix similar to svn#54948 so that the predicate does a text search when doing an update.
UPDATE "public"."some_datatypes1" SET "col1_bytea"='123456' WHERE CAST("col1_polygon" AS TEXT) = '((2,3),(12,23))'
This does work with primitive datatypes.
UPDATE "public"."some_datatypes1" SET "col1_bytea"='313233343536' WHERE col1_integer = 123456
Need more investigation with TDE.
I looked up the customer support email for this issue. Customer requested to support editing of macaddr, inet, cidr, and uuid data types.
Editing of uuid data type is already supported.
I've enabled editing of macaddr, inet, and cidr data types in beta-29.
I looked up the customer support email for this issue. Customer requested to support editing of macaddr, inet, cidr, and uuid data types.
Editing of uuid data type is already supported.
I've enabled editing of macaddr, inet, and cidr data types in beta-29.
I have verified the TDE for macaddr, inet, bytea and cidr data types.Now, these data type columns are editable and we can insert values successfully via TDE.Please refer this.
I have also tested the import for Batch and Full transaction modes for these data types.Please refer this.
Arrays are scripted and displayed correctly. please refer this.
Verified in ADS 19-beta-32
I have verified the TDE for macaddr, inet, bytea and cidr data types.Now, these data type columns are editable and we can insert values successfully via TDE.Please refer this.
I have also tested the import for Batch and Full transaction modes for these data types.Please refer this.
Arrays are scripted and displayed correctly. please refer this.
Verified in ADS 19-beta-32
Verified in ADS v19.0.0-beta-32. "macaddr, inet, and cidr" data types is editable in Table Data Editor for PostgreSQL
Verified in ADS v19.0.0-beta-32. "macaddr, inet, and cidr" data types is editable in Table Data Editor for PostgreSQL
Issue #13731 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 19.0.0-beta-29 |
| No time estimate |
Turned on editing AFTableColumnInitPostgreSQL for the following: