C
ChUIMonster
Guest
For those who are not following the CCS forum (or perhaps haven't joined it...) We're trying to get a spec going to define a baseline set of storage areas that ought to be the absolute minimum for a database in order to cure the "everything gets dumped in the schema area" problem. Interested parties are invited to join us over at: https://community.progress.com/products/directions/common_component/f/208/t/27321 You might also find this interesting: (Please visit the site to view this file) Executive Summary This document contains a proposal to the Common Component Standards (CCS) Steering Committee to form a new project team whose goal it is to produce a specification for Basic Storage Areas to define a minimum collection of storage areas for an application using an OpenEdge database The following sections of the document describe in general terms what the component is, the benefits it provides to application developers, and what the team’s deliverables would be. Component Description Explain the purpose and architecture of the component. The purpose of this specification is to describe the minimum, basic, set of storage areas that should be defined for any application that uses an OpenEdge database and to give a specific recommendation beyond the generic statement that “applications should not store user objects in the schema area”. Benefits and Use Cases Explain the benefits and expected use cases for the component. Currently application partners and other developers have no guidance to help them determine an appropriate set of storage areas for their applications. The only advice from Progress is that no user objects (tables, indexes or large objects) should be assigned to the schema area. Yet, by default, the only area available is the schema area and, by default, the schema area is the area that newly created objects are assigned to. As a result, nearly all new applications, conversions, upgrades and migrations leave the user objects in the schema area. All of the advanced features of the OpenEdge database rely upon type 2 storage areas. The schema area is always a type 1 area and objects in the schema area are, therefore, unable to participate in these advanced features. (It may not be relevant to the CCS process but a side effect is that revenue opportunities for Progress and partners are thus being squandered.) An explicit set of recommended minimum storage areas will help partners and developers to easily assign their storage objects to appropriate storage areas. This, in turn, will position their applications to be able to immediately leverage advanced features of the database without painful post-deployment maintenance (such as dumping and re-loading). Related / Dependent Common Component Specifications List all related and dependent specifications. Specifications can be submitted and worked on simultaneously. None known. Project Team Requirements List the expected timeframe and deliverables of the project team for this specification project. It should be possible to define this specification using a small team (4 to 6 people) in a relatively short time frame – perhaps 60 to 90 days. The major deliverables of this specification: Structure file defining the recommended storage areas White paper describing: the areas and how they should be used how to safely extend the areas for advanced uses Scripts for converting existing schema-only database definitions to the new spec
Continue reading...
Continue reading...