Bug 123448 - dbchange does not handle triggers and stored procs
dbchange does not handle triggers and stored procs
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karen Jacqmin-Adams
Fanny Augustin
Depends On:
Blocks: 117781
  Show dependency treegraph
Reported: 2004-05-18 12:53 EDT by Karen Jacqmin-Adams
Modified: 2007-10-23 22:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-18 11:47:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Karen Jacqmin-Adams 2004-05-18 12:53:51 EDT
Description of problem:
The dbchange script parses scripts into individual statements by
semicolons.  This does not work for triggers and stored procs which do
contain semicolons within their definition.
Comment 1 Karen Jacqmin-Adams 2004-05-21 19:16:01 EDT
#  How was this issue addressed?
Function _parse_procs was added to DBChange.pm.

# What level of users are affected? (Such as, All, Mgmt. Satellite
only, Mgmt. Satellite and Proxy, Mon. Satellite only, Mon. Satellite
and Scout.)

RHN Dept/DBA who have used the dbchange tools.

# Where specifically can the change be seen?
Not visible in an app.

# If the change cannot be verified visually, how should it be tested?
Use the dbchange tool to insert stored procedures, functions,
triggers, and packages into a test database.
Comment 2 Karen Jacqmin-Adams 2004-05-28 10:40:14 EDT
Peter also added some code to support anonymous procedures.  

Nick has built an rpm which has been released to 
rhn/build/support-rhel3/RPMS.  Moving to ON_DEV status.

Note You need to log in before you can comment on or make changes to this bug.