tag:blogger.com,1999:blog-8449039.post5637706622193756324..comments2024-03-28T05:59:36.577-04:00Comments on Scott Spendolini's Blog: Look, But Don't TouchScotthttp://www.blogger.com/profile/01187435106015051061noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8449039.post-56486845239704671312010-03-08T03:38:57.739-05:002010-03-08T03:38:57.739-05:00Thanks John for the interesting post. (and for you...Thanks John for the interesting post. (and for your half of the excellent book "Pro Application Express). <br /><br />I've recently encountered an issue within Apex which at the moment I can't see a way around without doing what you have said not to do! <br /><br />I posted the question over on stackoverflow (http://stackoverflow.com/questions/2371115/what-options-do-i-have-to-change-wsdl-location-for-a-web-service-used-within-apex)<br /><br />Is this the exception to the rule? or is there a better way to do this?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8449039.post-70786491315194468082010-01-31T10:24:50.113-05:002010-01-31T10:24:50.113-05:00I think we can all say that we've all modified...I think we can all say that we've all modified something that we shouldn't have at some point in our careers. Sometimes it worked; others, well... not so much.<br /><br />The main points that you both brought up is that <br /><br />1) don't do it <br />2) when break rule #1, be REALLY careful and <br />3) understand that if you break it, you bought it, so to speak<br /><br />As nice and good as the APEX team is, I don't think that they can afford to be in the business of writing custom patches to bail out customers time and time again.<br /><br />- Scott -Scotthttps://www.blogger.com/profile/01187435106015051061noreply@blogger.comtag:blogger.com,1999:blog-8449039.post-24253484142129924632010-01-31T03:54:00.561-05:002010-01-31T03:54:00.561-05:00I agree in principle, however...
I mean, there sh...I agree in principle, however...<br /><br />I mean, there should not be any need to stress the fact that who is changing things in the database using unsupported methods is embarking on an adventure of his own and there is no obligation for Oracle to restore things to a prior state. It's like saying if you jump off a cliff, you'd better off bringing your own parachute, don't expect the landing to be soft.<br /><br />With this clear statement in mind, i spent most of the last 25 years "poking around" because that is the only way to understand things more deeply, it's the black box approach.<br /><br />As you remarked however, this must be done in a controlled environment, where you can easily revert the system to its working state.<br /><br />Clearly sometimes i happened to forgot to take a backup first... :-DByte64https://www.blogger.com/profile/15629209362377395020noreply@blogger.comtag:blogger.com,1999:blog-8449039.post-39188731219466837972010-01-30T22:32:41.074-05:002010-01-30T22:32:41.074-05:00I recall amending Forms 3.0 inp files in an editor...I recall amending Forms 3.0 inp files in an editor rather than through the application.<br /><br />The point of rules is to make you think twice about what you are doing before you break themSydOraclehttps://www.blogger.com/profile/08828771074492585943noreply@blogger.com