tag:blogger.com,1999:blog-6523639693581093902.post1194631614111423911..comments2022-03-02T01:53:39.569-08:00Comments on Oracle APEX by Nandini Thakur: Interactive report Bug in Oracle APEX Development Tool NandiniLearninghttp://www.blogger.com/profile/08866420666128058793noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-6523639693581093902.post-29968008235735984212013-02-13T06:42:28.479-08:002013-02-13T06:42:28.479-08:00But why so ? in that case , Standard reports are b...But why so ? in that case , Standard reports are better than interactive report . as they need not require to touch the report again when the db level changes are madeNandiniLearninghttps://www.blogger.com/profile/08866420666128058793noreply@blogger.comtag:blogger.com,1999:blog-6523639693581093902.post-36695116106792950932013-02-13T06:40:33.441-08:002013-02-13T06:40:33.441-08:00forget about appearing in the report , the IR rep...forget about appearing in the report , the IR report is giving oracle error as column does not exists , soon i land on my page .<br /><br />The same query <br />select * from my_view doesnot give me any error . NandiniLearninghttps://www.blogger.com/profile/08866420666128058793noreply@blogger.comtag:blogger.com,1999:blog-6523639693581093902.post-21507184976201384092013-02-13T06:38:14.425-08:002013-02-13T06:38:14.425-08:00Hi good_practice_dude ,
My question was actually ...Hi good_practice_dude ,<br /><br />My question was actually not to check the coding standard , but i want to check that<br />when<br /> select * from my_view , column change doesn't give problem in Standard report , why does it give Oracle error in interactive report .<br /><br /><br />as both should probably execute the query when the page runs , so why one is not giving error and another is giving error .NandiniLearninghttps://www.blogger.com/profile/08866420666128058793noreply@blogger.comtag:blogger.com,1999:blog-6523639693581093902.post-5860517828049624602013-01-27T10:45:59.810-08:002013-01-27T10:45:59.810-08:00Please do not write a select as 'select *'...Please do not write a select as 'select *'<br /><br />The best way to write is <br />select mv.my_id my_id<br /> ,mv.my_name my_name,<br /> ,mv.my_status my_status<br /> from my view mv<br /><br />This will bomb the report as the column name changed.<br />You can then change the query to<br /><br />select mv.my_id my_id<br /> ,mv.my_name my_name,<br /> ,mv.active_status my_status<br /> from my view mv<br />good_practices_dudehttp://www.google.comnoreply@blogger.comtag:blogger.com,1999:blog-6523639693581093902.post-42565965796804161222013-01-24T20:20:17.653-08:002013-01-24T20:20:17.653-08:00I think what you are expecting the new column &quo...I think what you are expecting the new column "Active_status" to appear automatically in the IR after the above change, but the bad news is it will not happen. <br /><br />You need to run the IR and click on "Reset" option from the dropdown and will see the newly added changed column "Active_status" and don't forget to click on "Save" option and also selecting "Primary Report". Hope this helps you.Sathish Kumar JShttps://www.blogger.com/profile/11997510099609681817noreply@blogger.comtag:blogger.com,1999:blog-6523639693581093902.post-57092279376764364092013-01-24T08:26:39.736-08:002013-01-24T08:26:39.736-08:00While this may not be what you expected, it is act...While this may not be what you expected, it is actually accurate behavior. When you enter a SQL Statement into an Interactive Report, the builder parses the SQL statement and stores the column information in the metadata. The metadata is then used at runtime to allow users to decide which columns they want to see, which to use for column breaks, etc. <br /><br />If something changes in the underlying table (or view) you need to go back and at least "touch" the statement so that the metadata can be rewritten and any new columns can be added, and any deleted columns will be removed.<br /><br />Doug Gaulthttps://www.blogger.com/profile/16786329323466667017noreply@blogger.comtag:blogger.com,1999:blog-6523639693581093902.post-30467758809899130182013-01-23T09:32:02.053-08:002013-01-23T09:32:02.053-08:00This comment has been removed by a blog administrator.Unknownhttps://www.blogger.com/profile/11591265827051316173noreply@blogger.com