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 | pranav.jadhao(*) |
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | DB - MySQL |
| Version | 19.0 |
|
|
180 KB
|
197 B
|
|
60 KB
Reproducible in v15 and v16 builds.
Issue is also reproducible when use script in attached .sql file instead of creating table through visual editor.
If the object is created via SQL scripts & then a SCRIPT CREATE action is performed, is the generated script accurate?
If the object is created via SQL scripts & then a SCRIPT CREATE action is performed, is the generated script accurate?
If the object is created via SQL scripts & then a SCRIPT CREATE action is performed, is the generated script accurate?
>>No, the generated script via SCRIPT CREATE action is incorrect. Same scripting issue is reproducible here.Please see this screenshot.
If the object is created via SQL scripts & then a SCRIPT CREATE action is performed, is the generated script accurate?
>>No, the generated script via SCRIPT CREATE action is incorrect. Same scripting issue is reproducible here.Please see this screenshot.
Work related to this is currently being done in a VA issue #8396. This issue won't be reproducible once issue #8396 is resolved.
Work related to this is currently being done in a VA issue #8396. This issue won't be reproducible once issue #8396 is resolved.
As specified in this document, For storage engines other than InnoDB 'foreign keys' are not actually stored or used in MySQL 5.0, 5.1. They are only parsed, And as per document before MySQL 5.5.5 default storage engine is MyISAM. Due to this Foreign key is not being shown here. If we use InnoDB as a storage engine for creating the table then the Foreign key is extracted correctly.
As per the above description, current ADS behavior is as expected due to limitations from server side so, Marking this issue as won't fix.
As specified in this document, For storage engines other than InnoDB 'foreign keys' are not actually stored or used in MySQL 5.0, 5.1. They are only parsed, And as per document before MySQL 5.5.5 default storage engine is MyISAM. Due to this Foreign key is not being shown here. If we use InnoDB as a storage engine for creating the table then the Foreign key is extracted correctly.
As per the above description, current ADS behavior is as expected due to limitations from server side so, Marking this issue as won't fix.
As per the Pranav's comment, I am marking this issue as Verified.
As per the Pranav's comment, I am marking this issue as Verified.
Issue #13536 |
| Closed |
| Won't Fix |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
Reproducible in v15 and v16 builds.
Issue is also reproducible when use script in attached .sql file instead of creating table through visual editor.