


Links to Item pages that use the linker template will be colorized to match the Quality of the item so long as the quality is set in the linker call. Complete documentation for this can be found at Directives. The format for a redirect is: #redirect ]. For many items that have mutliple versions for different "grades" we will create a single item entry, such as Elixir of Life, build a table there which lists all the variations and their effects, and then add redirects from the individual names to the single page. Quest rewards, and crafting-related items are definitely in the "do" list. What we will try to do is document any item that is of exceptional shininess, is required by a quest or other task, or is so common that not to have it listed would be absurd. That would be an impossible and never-ending task. Oracle did actually dump core after I did that so better not.We are not, at this time, attempting to document every single item available in this game. Since it is a column we can obviously select it as well.SQL> select SYS_NC00014$ from d where object_id=500 A column can go in the where clause, even pseudo-columns.SQL> select object_name from d where sys_nc00014$='T' dynamic sampling used for this statement Predicate Information (identified by operation id): | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | SQL> select object_name from d where upper(status)='T' Some tests then.SQL> set autotrace traceonly exp so Oracle will index the same pseudo column! Eureka! Thats the index bit, we got two indexes with the same "function", SQL> create index d_2 on d(object_id,upper(status),timestamp) SQL> select index_name,column_expression from user_ind_expressions SQL> select index_name,column_name from user_ind_columns where table_name='D' Let's index it with some pseudo stuff.SQL> create index d_1 on d(upper(status)) SQL> create table d as select * from all_objects They are indeed pseudo-columns, or calculated columns as I think Oracle wants to call them in 11g. However, when playing around with some composite indexes including functions today I finally got it. Never thought much about investigating it either. I never really understood the whole thing about it, sure I figures one could consider it a pseudo-column as it was sort of a calculated value that was stored in the database. All the cool people I meet at Oracle events keep referring to "function based indexes" as pseudo-columns.
