Support for materialized view in Sybase ASE 15.7+
A new feature request for Sybase ASE 15.7+ materialized views.
Take a look at
Currently I am unable to find catalog support for this object type. They have not documented the statement in there online docs as well. Customer may want to file an issue with sybase to provide catalog data support for this object. pushing issue to future
Can you see the Materialized View in Sybase Central? What does the GUI look like? If so, how are they extracting?
Are the objects in sysobjects?
Can you see the Materialized View in Sybase Central? What does the GUI look like? If so, how are they extracting?
Are the objects in sysobjects?
NOTES :
In case you cannot extract the definition using the catalog procedures, I'd say its definition can be easily extracted from the syscomments system table. This won't include of course the indexes/constraints created on the view.
As an additional request on the issue, it would be very useful to have a visual indicator (perhaps on the icon or color of the materialized view name or ...) to show whether or not the view is damaged.
As stated in my previous mail, a materialized view gets damaged after any change (even just a reorg rebuild) on one of the base tables. You can still select on the view and it will still return the results it has, but it doesn't get updated with new information - 'Silent failure'. According to SAP support this is expected behaviour and they will clarify the documentation on that.
Therefore, it is very useful to know whether the view is still working or flagged damaged.
Sysobject contains a flag that indicates whether an object is damaged or not.
NOTES :
In case you cannot extract the definition using the catalog procedures, I'd say its definition can be easily extracted from the syscomments system table. This won't include of course the indexes/constraints created on the view.
As an additional request on the issue, it would be very useful to have a visual indicator (perhaps on the icon or color of the materialized view name or ...) to show whether or not the view is damaged.
As stated in my previous mail, a materialized view gets damaged after any change (even just a reorg rebuild) on one of the base tables. You can still select on the view and it will still return the results it has, but it doesn't get updated with new information - 'Silent failure'. According to SAP support this is expected behaviour and they will clarify the documentation on that.
Therefore, it is very useful to know whether the view is still working or flagged damaged.
Sysobject contains a flag that indicates whether an object is damaged or not.
New Tree node [Materialized Views] added to sybase ase 15.7+. Extraction/Scripting support added. Schema Script Generator support and multi-object scripting support added. Object search support added for mat views by object name, column name and view source.
Detail Information added. The mat view is still using the view icon and the invalid view icon when the state of the mat view is set to broken.
New Tree node [Materialized Views] added to sybase ase 15.7+. Extraction/Scripting support added. Schema Script Generator support and multi-object scripting support added. Object search support added for mat views by object name, column name and view source.
Detail Information added. The mat view is still using the view icon and the invalid view icon when the state of the mat view is set to broken.
Issue #11113 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v17.0.0-alpha-4 |
No time estimate |
2 issue links |
relates to #10689
Issue #10689Support for "in row" feature and research for any other new options in Sybase ASE 15.7+ |
relates to #13701
Issue #13701Throws "java.lang.ClassFormatError: \\/\\/\\हिñçêČάй語简�?한\\/A͊ꌉꀷꍳintfinally" when we Script Object to window as/new window as/File as->CREATE for materialized views. |
Currently I am unable to find catalog support for this object type. They have not documented the statement in there online docs as well. Customer may want to file an issue with sybase to provide catalog data support for this object. pushing issue to future