Re: Am I too hard on the developper ?

Thanks to all who replied. Basically, a majority of DBA would keep the grants for themselves. As for understanding the developpers, I think I understand them quite well as I've developped with sql*forms and pl/sql 6 years before becoming a dba. The thing here is that there is a lot politics as

RE: Am I too hard on the developper ?

On Fri, 16 Feb 2001 [EMAIL PROTECTED] wrote: ... > DBAs who seem to look down on developers. There are good and bad > developers, but guess what ... there are also good and bad DBAs. We've had > both here. True, but bad developers tend to last longer than bad DBA's. ;) Jared -- Please see

Re: Am I too hard on the developper ?

Speaking as both a DBA and a developer, I require myself to put every grant into a script table when I develop an application. This why the grants, tables, indexes, views, etc can be rebuilt at will. and speaking as a DBA, Alter the damn table and modify your create scripts. >>> paquette step

RE: Am I too hard on the developper ?

. :) >From: [EMAIL PROTECTED] >Reply-To: [EMAIL PROTECTED] >To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> >Subject: RE: Am I too hard on the developper ? >Date: Fri, 16 Feb 2001 10:50:29 -0800 > >From a developer: > >1. Although it may not always

RE: Am I too hard on the developper ?

Comments inline: > > >From a developer: > >1. Although it may not always matter at the database level, the order of >the columns within a table often follow a logical sequence. ALTER TABLE >does not give you control over where in the column list that column will be >added. Example: If you wa

Re: Am I too hard on the developper ?

I'd probably work with 'em on it, and most likely I'd point them to USER_TAB_PRIVS so that they could do their own regranting. Or I might do it for 'em. But I wouldn't drop everything to accommodate them. Whenever I got a request like this as a DBA, I would try to estimate how long it would take a

RE: Am I too hard on the developper ?

I think his/her database is 7.x not 8.x. You can drop,move, all these good things in 8.x only. --- "Gogala, Mladen" <[EMAIL PROTECTED]> wrote: > Stephane, the idea of dropping and re-creating > tables is simply > preposterous. If the tables involved are bigger then > 50M, then > such procedure

Re: Am I too hard on the developper ?

Yeah but it is so much work to add 10 new fields . The latest one is 'Do we have a tool that can compare the dev and the test environment so we know what we have to put in test ?' . Not only it is too hard to do 10 alter tables but also it is too hard to make a list of what is changed (I'm not e

Re: Am I too hard on the developper ?

Consider yourself lucky. Last week I had a doh!veloper tell me (I swear I'm not making this up) that he had to test his code in production because "the test environment got messed up and its too hard to figure out how to make it right again". He's a really junior guy and actually quite brilli

RE: Am I too hard on the developper ?

>From a developer: 1. Although it may not always matter at the database level, the order of the columns within a table often follow a logical sequence. ALTER TABLE does not give you control over where in the column list that column will be added. Example: If you want to add a MIDDLE_NAME colu

Re: Am I too hard on the developper ?

Stay on it. Dropping tables to add columns in development is just plain stupid. Jared On Fri, 16 Feb 2001, [iso-8859-1] paquette stephane wrote: > Hi, > > I do not know if it's friday afternoon or what ? > The developpers want me to regenerate the grants in > the development environment becau

Re:RE: Am I too hard on the developper ?

Mladen, Can I interest you in a change of location??? :-) Dick Goulet Reply Separator Author: "Gogala; Mladen" <[EMAIL PROTECTED]> Date: 2/16/2001 9:02 AM Stephane, the idea of dropping and re-creating tables is simply preposterous. If the tabl

Re: Am I too hard on the developper ?

Yeah but it is so much work to add 10 new fields . The latest one is 'Do we have a tool that can compare the dev and the test environment so we know what we have to put in test ?' . Not only it is too hard to do 10 alter tables but also it is too hard to make a list of what is changed (I'm not e

RE: Am I too hard on the developper ?

te stephane [mailto:[EMAIL PROTECTED]] Verzonden: vrijdag 16 februari 2001 17:06 Aan: Multiple recipients of list ORACLE-L Onderwerp: Am I too hard on the developper ? Hi, I do not know if it's friday afternoon or what ? The developpers want me to regenerate the grants in the development enviro

Re: Am I too hard on the developper ?

gt;To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> >Subject: Am I too hard on the developper ? >Date: Fri, 16 Feb 2001 08:05:37 -0800 > >Hi, > >I do not know if it's friday afternoon or what ? >The developpers want me to regenerate the grants in >the develop

RE: Am I too hard on the developper ?

Stephane, the idea of dropping and re-creating tables is simply preposterous. If the tables involved are bigger then 50M, then such procedure is not practical. Anyway, I don't see why would the table need to be dropped/re-created now when we can drop columns and move/rebuild tables. Fortunately

Re: Am I too hard on the developper ?

Stephane, stick to your guns - part of the dba's job (as I see it, and try to do ) is to help guide the developers in the best way to do things on the database if it's your choice that they should do an alter table, then that's what they should do. don't give in. Brian. paquette stephane <

Am I too hard on the developper ?

Hi, I do not know if it's friday afternoon or what ? The developpers want me to regenerate the grants in the development environment because they're running a script that drops and recreates a new version of the tables. I asked them : Could you do an alter table instead ? The developpers : What