Comments
4 comments
- 
                
                   May I ask what the use case of this feature is? When would you not want the schema to be specified? May I ask what the use case of this feature is? When would you not want the schema to be specified?
- 
                
                   Hi Simon, Hi Simon,
 We have many environments including several development, testing, staging and live environments.
 These environments get installed with different user names/schemas so the ability to compare and make the generated script more generic by not including the schemas name is useful to us and can subsequently be used to upgrade/downgrade many of these different environments with the same script without having to manually change the schema name across environments.
 It's not a major feature but more of a nice to have.
 Hope this helps.
 Lee.
- 
                
                   Hi Lee, Hi Lee,
 I've added this request to our backlog as OC-152 - I can see how it would help to create more generic scripts.
 We're trying to tie down the features for v1 now, so I'm afraid I can't guarantee that this will make it in for v1. Customer requests always add weight to a feature request though, so thanks for raising it.
 Thanks for all your feedback so far - please let us know if you have any further comments, feature requests, or issues.
 Thanks,
 Alice.
- 
                
                   Hi Alice, Hi Alice,
 Thanks for that, it certainly would be a most helpful and useful enhancement for us.
 Regards,
 Lee.
Add comment
Please sign in to leave a comment.
Just another feature enhancement request. When synchronising to a script it would be useful to have the option not to have the the schema/user name included in the script. E.g Create Table "SCHEMA"."MYTABLE" is what is created now but capability to switch this off so would output Create Table "MYTABLE"
Not a major one as can do a find and replace to make the synch script more generic but a nice to have.
Regards,
Lee.