On Thu, May 20, 2010 at 9:45 AM, Kirby Leeper <[email protected]> wrote:
> Carey, I hate to butt-in here but why not just put all those computed > fields > in a table VIEW in the database itself and let the db just present the rows > to Dabo as if they really were in the table? > > IE: > Create VIEW xyz as > SELECT col1, col2, col3, > col1/col2 as col4, > col1*col3 as col5 > from table xy where ... > > <http://leafe.com/archives/byMID/[email protected]> > Please do butt-in. Sharing ideas is how we learn, and the purpose of forums such as this. I'm not sure I understand what you are saying. It sound to me like you are saying I can create an in memory table view. Perhaps I should explain further. I have an sqlite db with 4 tables: Customer Table: fields are: ID and Name Project Table: fields are: ID and Name Task Table: fields are ID and Name Records Table: fields are: ID, customerID, projectID, taskID, start time, and end time. I created the duration field as a virtual filed in the records table by subtracting start time from end time. Being a virtual field it as calculated as needed and doesn't actually exist in the database I'm don't understand what you're proposing above. Carey --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
