tag:blogger.com,1999:blog-8884584404576003487.post5694231017193171399..comments2024-02-29T09:43:12.251-05:00Comments on ORACLENERD: 11g New Feature: Virtual Columnsoraclenerdhttp://www.blogger.com/profile/12412013306950057961noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8884584404576003487.post-6752776873552630352008-07-31T09:52:00.000-04:002008-07-31T09:52:00.000-04:00That makes sense (same as a view or query). Not h...That makes sense (same as a view or query). Not having used it in production yet, I don't know what the pitfalls might be.<BR/><BR/>And defining the %ROWTYPE is a good example of how it might affect future programming...<BR/><BR/>Thanks for the pointers Gary.<BR/><BR/>chetoraclenerdhttps://www.blogger.com/profile/12412013306950057961noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-80002510522122721222008-07-30T23:18:00.000-04:002008-07-30T23:18:00.000-04:00"If the expression is complex it might slow it dow..."If the expression is complex it might slow it down."<BR/>Should be any different from the same expression in a view or a query. However if you are collecting stats on the column (and is there a point to them if you aren't) then it may impact the duration of the stats gathering.<BR/>One thing I noted, now I've used it live, is that you can't do an INSERT INTO table SELECT or INSERT INTO table VALUES.<BR/>Because the virtual column is derived it can't be set manually, so you have to explicitly define all the columns you are allowed to set.<BR/>That can make it a pain if you are in the habit of defining PL/SQL records as TABLE%ROWTYPE. I'd recommend a view on the table that excludes the virtual column(s) so your inserts can be done through the view.SydOraclehttps://www.blogger.com/profile/08828771074492585943noreply@blogger.com