As for prefixing tables and views I absolutely hate that practice. Give a person no information at all before giving them possibly bad information. Anyone browsing a db for objects can quite easily tell a table from a view, but if I have a table named tblUsers that for some reason I decide to restructure in the future into two tables, with a view unifying them to keep from breaking old code I now have a view named tblUsers. At this point I am left with two unappealing options, leave a view named with a tbl prefix which may confuse some developers, or force another layer, either middle tier or application to be rewritten to reference my new structure or name viewUsers. That negates a large part of the value of views IMHO.
In March 2015, the Australian Competition and Consumer Commission (ACCC) launched proceedings against Reckitt Benckiser; for misleading advertising for its targeted pain range. In December 2015, the Federal Court of Australia found that Reckitt Benckiser, which makes Nurofen, had misled consumers with its "Nurofen Specific pain range", and ordered that all Nurofen specific pain products be removed from retail sale within three months.  A spokeswoman for Reckitt Benckiser argued that, "[This] specific-pain range" was intended "to help consumers navigate their pain relief options, particularly within the grocery environment where there is no healthcare professional to assist decision making".  The ACCC said that the products were found to be "no more effective at treating the type of pain described on its packaging than any of the other Nurofen specific pain products", and sold for almost twice the price.  Specific pain range painkillers include Nurofen Back Pain, Nurofen Period Pain, Nurofen Migraine Pain and Nurofen Tension; and all contain the "same active ingredient, 342 milligrams of ibuprofen lysine".