Package Explorer
Wrapped Vs. Unwrapped Packages

Wrapped Vs. Unwrapped Packages

Wrapped packages are marked with the package icon , whereas unwrapped packages appear with the package icon

. An unwrapped code package consists of a .cpa file that serves as the root node of the package, as well as folders and SQL files that are stored separately on the file system, under the same folder of the .cpa file. In other words, an unwrapped package is very similar to a Solution in a Visual Studio® .Net project. Using unwrapped package, developers can check-in and check-out different SQL files and folders in the code package, and work in collaboration on their database code releases.

The root node of an unwrapped code package is stored as a .cpa file. This file holds all the properties of the code package, such as the name and location of folders and SQL scripts in the package, the Container mapped to each script, and so on. To visualize an example of an unwrapped package, please refer to the image below.

Note: A new code package is always created as an unwrapped package.

Figure 78:  An unwrapped package (left) and the way it is stored on the file system (right).

A wrapped package, unlike an unwrapped package, is a single .cpa file that contains the content of all SQL scripts included in the package. In other words, a wrapped code package is stored in the file system as a single .cpa file.

When developers complete composing their release, they can wrap the unwrapped code package by right-clicking the package node and selecting the Wrap option in the context menu. Similarly, wrapped packages can be unwrapped by right-clicking the Wrapped package node and selecting the unwrap option from the context menu.

In order to find out whether a package is wrapped or unwrapped, click on the package node and press F4 to bring up the properties window.

Figure 79:  Examining the Wrapped package property.

© 2001-2018 JNetDirect, Inc. All Rights Reserved.