Hi

Would it be possible to get clarification on when views need to be 'updated'.

While Developing an Application I've occasionally run in to a couple of issues when changing DB table structure which is referenced in views.

If I have a view with a Select * in it, Adding Fields to the Table its derived from sometimes causes incorrect fields to be returned to the application, and sometimes when changing data types in the source tables, the previous types are still represented.

Altering the view and saving it seems to sort this out, and I'm assuming its something to do with the view being prepared once prior to use, but when I deploy I'm just wondering if I need to drop and re-create all views if the source tables are changed.

Thanks in Advance.

Chris,

<< Would it be possible to get clarification on when views need to be
'updated'. >>

Never - they are automatically updated by EDB as necessary.

<< While Developing an Application I've occasionally run in to a couple of
issues when changing DB table structure which is referenced in views.

If I have a view with a Select * in it, Adding Fields to the Table its
derived from sometimes causes incorrect fields to be returned to the
application, and sometimes when changing data types in the source tables,
the previous types are still represented.

Altering the view and saving it seems to sort this out, and I'm assuming its
something to do with the view being prepared once prior to use, but when I
deploy I'm just wondering if I need to drop and re-create all views if the
source tables are changed. >>

This is a bug.  I just did a test here and the issue is that the view is not
being re-compiled when the underlying tables change, so I'll make sure this
is fixed in the next EDB build.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

OK, Thanks for letting me know.

"Tim Young [Elevate Software]" wrote:

This is a bug.  I just did a test here and the issue is that the view is not
being re-compiled when the underlying tables change, so I'll make sure this
is fixed in the next EDB build.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com