Re: postgresql vs mysql

> That's why you make a table for every device or every measurement, and
> then use a view to consolidate it.  With update-able views, there's no
> excuse not to.

I would be interested on here some of your experiences on this?

I've built and made use of table hierarchies three levels deep and about twenty classification
types wide that I rolled up into separate update-able view.  However, I found the process of
cascading the updates to all three levels of each classification type using the "TID" rather
tedious.

Regards,
Richard Broersma Jr.