7 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• AdminMichael Christofides (Product Manager - Oracle tools, Red Gate) commented  ·  February 27, 2013 4:43 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @Leigh - hopefully we've now addressed 1. Regarding 2 and 3, we appreciate your feedback. Currently our Schema Compare tool can be used to get around this, as it can script out files from schemas and can also be used for creating deployment scripts between environments. It is as yet undecided how we solve this problem for Source Control users who aren't going to use Schema Compare for deployments. Thanks for the migration feature suggestion, duly noted.

  @Curtis - I'm delighted this now works for you, and will close this issue.

• Curtis commented  ·  February 26, 2013 12:09 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This works fine in our environment now since we have more flexibility in where we check out the code in our repository. As long as we follow the naming convention you have suggested we can run the scripts against production to create/update the affected objects for the version.

• Leigh commented  ·  February 22, 2013 5:36 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Michael, it sounds like you are bending over backwards to make the app operate nicely for shops that 1) Only use root folders for schema names 2) Use folder names that match production schema names but not dev/qa and 3) Aren't interested in running scripts on anything but production. This seems like an extremely narrow subset of customers you are catering too. I suggest you make the schema name in the script match the schema name in the database and then create a separate migration feature that could do schema name translation.

• Curtis commented  ·  February 15, 2013 8:28 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I think if you fix this http://redgate.uservoice.com/forums/174014-oracle-tools/suggestions/3652032-allow-source-control-in-sub-folders-of-repository then it will make this work better in our environment.

• Curtis commented  ·  February 14, 2013 8:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Neil did you make progress on this one?

• AdminNeil Anderson (Software Engineer, Red Gate) commented  ·  February 8, 2013 12:45 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hi Curtis,

  Thanks for this. I'll have a look into it today and be in touch.

  Neil

• Curtis commented  ·  February 7, 2013 10:37 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Update on this, it appears that this is the case in all scripts NOT just the UserObjectPrivs folder. Let me know if you need anymore information.