:
Sent by: Subject: RE: How-To or Good
Practices on Code Releases
[EMAIL PROTECTED]
m
November 13,
2002 12:15 PM
Please respond
to ORACLE-L
Rajesh.Rao,
I have the same experience. Developers directly connected to
production database and added a column with default table on a huge table. The whole
table is locked for 1 hour and other transaction failed.
Add a column with non default value and then
what is the difference in the db between adding a column with a default
value, and adding a column and then later modifying it to set a default
value?
in neither case is the value actually set in the column itself.
thx
-b
-Original Message-
Sent: Thursday, November 14, 2002 6:09 AM
To:
Magaliff, Bill wrote:
what is the difference in the db between adding a column with a default
value, and adding a column and then later modifying it to set a default
value?
in neither case is the value actually set in the column itself.
thx
-b
Give it a try, Bill.
--
Regards,
:
Subject:Re: RE: How-To or Good Practices on Code Releases
Rajesh.Rao,
I have the same experience. Developers
directly connected to production database and added a column with default
table on a huge table. The whole table is locked for 1 hour
Title: How-To or Good Practices on Code Releases
Friends ...
I have a (sort of) problem ... what are the best practices to manage code releases to production environment ...
currently we get a bunch of scripts from development team, and we release code to production on the schedule
Title: How-To or Good Practices on Code Releases
Whenever I install a new release of software my
boss wants to know:
How do you return to the old version if this does not
work?
For each install script require an undo
script.
We are using toad to compare schemas and it can also
generate
Title: How-To or Good Practices on Code Releases
TOAD _until now_ had problems with 9.2 database ... it would complain
that (in our case) 903 objects were not found when I could go in, and perform
all kind of DML on those objects.
7.4 seems to be better ...
Raj
The releases should be tried in the Development environment first. Then a
UAT (User Acceptance Test) environment, then production. The UAT
environment is usually a duplicate of the production environment. This is
the environment that you implement the changes , then test to see if the
changes
:
Sent by: Subject: Re: How-To or Good Practices on
Code Releases
root@fatcity
Title: How-To or Good Practices on Code Releases
Are you working with UTF8?
They had some problems in the initial release but they are
corrected now.
Yechiel AdarMehish
- Original Message -
From:
Jamadagni, Rajendra
To: Multiple recipients of list ORACLE-L
Sent
.
Bailey/JPMCHATo: Multiple recipients of list
ORACLE-L [EMAIL PROTECTED]
SE@CHASE cc:
Sent by: Subject: Re: How-To or Good
Practices on Code Releases
root@fatcity
:
Sent by: Subject: RE: How-To or Good Practices
on Code Releases
[EMAIL PROTECTED]
m
: How-To or Good
Practices on Code Releases
[EMAIL PROTECTED
]
dware.comcc:
Sent by: Subject: RE: How-To or
Good Practices on Code Releases
[EMAIL PROTECTED]
November 13, 2002
02:23 PM
Please
]cc:
ate.ny.us Subject: RE: How-To or Good Practices
on Code Releases
Sent
cc:
Sent by: Subject: RE: How-To or
Good Practices on Code Releases
[EMAIL PROTECTED]
November 13, 2002
02:23 PM
Please respond
17 matches
Mail list logo