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 | Critical |
| Complexity | Unknown |
| Component | App - General |
| Version | 15.0 |
We added support for netezza 7.0.3 supporting schemas but in the process we missed enhancing gui's to correctly qualify the owern/schema to the objects. Will need to look through the objects and there gui's and make the needed changes to correctly support visual creations/modification to obects.
|
|
72 KB
|
747 B
|
|
525 B
|
|
2 KB
|
|
3 KB
|
|
76 KB
|
|
103 KB
Issue is actually that we allow the modification of schemas in netezza versions that don't support schemas. This gives the user the illusion that he can change the schema of the object when scripting does not allow for qualifying objects.
fixed... Netezza will no longer be able to change schema. if schema support is enabled you can set the schema when creating the table at that time only. Also no gui for changing owner.
fixed... Netezza will no longer be able to change schema. if schema support is enabled you can set the schema when creating the table at that time only. Also no gui for changing owner.
@Tariq
I have enabled multi-schema support and able to create table/View/Sequence/Synonyams in each schema.
@Tariq
I have enabled multi-schema support and able to create table/View/Sequence/Synonyams in each schema.
Issue #12378 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
Issue is actually that we allow the modification of schemas in netezza versions that don't support schemas. This gives the user the illusion that he can change the schema of the object when scripting does not allow for qualifying objects.