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 | Major |
| Complexity | Unknown |
| Component | Tools - ER Modeler |
| Version | 18.0 |
|
|
78 KB
|
|
105 KB
|
|
95 KB
|
99 KB
|
|
183 KB
|
|
111 KB
|
|
126 KB
|
|
204 KB
@rohit: I dont think this is IDEA related issue. We introduced the integration in after dev-78. This purtucular issue started occuring right after development for v18 started.
This issue also reproduce for Postgresql 9.5
This issue also reproduce for Postgresql 9.5
@tom: I am able to reproduce the issue in 18.0.0-devi-210, Build #: 50927 with Build Date: 2016-Aug-24 09:21:42 AM. Can you try in a QA build against OSX and let me know if you are able to reproduce the issue ?
@tom: I am able to reproduce the issue in 18.0.0-devi-210, Build #: 50927 with Build Date: 2016-Aug-24 09:21:42 AM. Can you try in a QA build against OSX and let me know if you are able to reproduce the issue ?
Version: 18.0.0-devi-211
The same issue is occurred in Amazon Redshift too. The tables with constraints primary key and unique key are getting error as:
Error while generating ER diagram:
KEYWORD IMMEDIATE
Screenshot is in the given link (amazon_redshift(18-devi-211).png)
Version: 18.0.0-devi-211
The same issue is occurred in Amazon Redshift too. The tables with constraints primary key and unique key are getting error as:
Error while generating ER diagram:
KEYWORD IMMEDIATE
Screenshot is in the given link (amazon_redshift(18-devi-211).png)
From Tom:
For this issue, it appears to be something related to the QA build or execution. I have not been able to make it fail in dev.
From Tom:
For this issue, it appears to be something related to the QA build or execution. I have not been able to make it fail in dev.
Version: 18.0.0-devi-233
The same issue is occurred in ParAccel too.
Error while generating ER diagram:
KEYWORD IMMEDIATE
Version: 18.0.0-devi-233
The same issue is occurred in ParAccel too.
Error while generating ER diagram:
KEYWORD IMMEDIATE
Version: 18.0.0-devi-240
The same issue is occurred in Teradata 15.0 and Teradata 14.0.
Error while generating ER diagram:
KEYWORD IMMEDIATE
Version: 18.0.0-devi-240
The same issue is occurred in Teradata 15.0 and Teradata 14.0.
Error while generating ER diagram:
KEYWORD IMMEDIATE
Version: 18.0.0-devi-241
The same issue is occurred for Greenplum too. Following is the error message displayed:
Version: 18.0.0-devi-241
The same issue is occurred for Greenplum too. Following is the error message displayed:
@vaibgoyal : pls determine definitively as to which build this issue first occurred in. Post a grid of your results. For instance, if you have narrowed it down to devi-45, then post results for both dev-45 & dev-44. Include screenshots for both builds.
By performing this analysis, we can then isolate which change most likely caused this issue.
@vaibgoyal : pls determine definitively as to which build this issue first occurred in. Post a grid of your results. For instance, if you have narrowed it down to devi-45, then post results for both dev-45 & dev-44. Include screenshots for both builds.
By performing this analysis, we can then isolate which change most likely caused this issue.
|
ADS Builds
|
Database | ||
| Greenplum (4.3.9.1, 4.3.6.2, 4.3.3.0, 4.2.8.5) | |||
| Linux | Windows | MAC | |
| ADS 18-devi-246 | Y | Y | Y |
| ADS 18-devi-5 [Broken Build] (This is the 1st build we received) | Y | Y | Y |
| ADS v17.0.9 | N | N | N |
| ADS v16 | N | N | N |
| ADS v15 | N | N | N |
| ADS v14 | N | N | N |
| N - No, this issue is not observed and it is working fine. | |||
| Y - Yes, this issue is observed. | |||
| Comments: | ||||||
| 1. This issue occurs for the tables having primary key constraints. | ||||||
| 2. This issue occurs for Greenplum DB versions 4.3.9.1, 4.3.6.2, 4.3.3.0, 4.2.8.5 for ADS v18.0.0-devi-246, ADS v18.0.0-devi-5. | ||||||
| 3. This issue does not occurs in ADS v17, v16, v15, v14. | ||||||
| 4. Please refer to the screenshots ADS v18-devi-5(Greenplum).png & ADS v17-0-9(Greenplum).png attached in the description of the issue. |
|
ADS Builds
|
Database | ||
| Greenplum (4.3.9.1, 4.3.6.2, 4.3.3.0, 4.2.8.5) | |||
| Linux | Windows | MAC | |
| ADS 18-devi-246 | Y | Y | Y |
| ADS 18-devi-5 [Broken Build] (This is the 1st build we received) | Y | Y | Y |
| ADS v17.0.9 | N | N | N |
| ADS v16 | N | N | N |
| ADS v15 | N | N | N |
| ADS v14 | N | N | N |
| N - No, this issue is not observed and it is working fine. | |||
| Y - Yes, this issue is observed. | |||
| Comments: | ||||||
| 1. This issue occurs for the tables having primary key constraints. | ||||||
| 2. This issue occurs for Greenplum DB versions 4.3.9.1, 4.3.6.2, 4.3.3.0, 4.2.8.5 for ADS v18.0.0-devi-246, ADS v18.0.0-devi-5. | ||||||
| 3. This issue does not occurs in ADS v17, v16, v15, v14. | ||||||
| 4. Please refer to the screenshots ADS v18-devi-5(Greenplum).png & ADS v17-0-9(Greenplum).png attached in the description of the issue. |
Verified in ADS 18.0.0-rc-11 in below databases
1 - PostgreSql 9.4
2 - PostgreSql 9.5
3 - Greenplum 4.3.11
4. Teradata 15
5. Amazon Redshift
Verified in ADS 18.0.0-rc-11 in below databases
1 - PostgreSql 9.4
2 - PostgreSql 9.5
3 - Greenplum 4.3.11
4. Teradata 15
5. Amazon Redshift
Issue #14583 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build devi-248 |
| No time estimate |
@rohit: I dont think this is IDEA related issue. We introduced the integration in after dev-78. This purtucular issue started occuring right after development for v18 started.