What you envisage was realized by the Pick database system from the
1970s. It had a "dictionary" to each table, and virtual fields could be
defined in the dictionary as expressions.
With SQL you might find that VIEWs and user defined functions might
adapt to your application.
JS
Eugen Stoianovici wrote:
My ideea was to create some database structure where some tables would
store the real data (the actual values of the columns) and some other
tables that have the values i need to work with calculated based upon
the data stored in the first tables. Triggers seem the way to go, but i
was wondering if there is another way...somewhere in the line of CREATE
TABLE sometable (somefield "SELECT bla bla")
I need to model some large wierd electical circuit with a lot of backup
lines and so on (we're talking huge..around 1000 switches). I'm trying
to find a way o partialy parsing this graph within the database before
passing it to my application for processing. I can generate some
scenarios when i first read the circuit and then create a database that
stores this info but..pocessing the graph real time is not an option.
