Jump to content

McQuillan

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0

About McQuillan

  • Rank
    I've come back for more.

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    2013

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi James, Thank you very much for replying, you've made some very interesting points and helped switched my perspective. You're right, I was using the DB as a CVT - which isn't sensible, and the many-tables one-row comment (instead of one-table, many-rows) seems so obvious now it's been pointed out! I'm going to mull it over and work on a better design on Monday. But I think I'm going to create a design using the following: For items that actually need to be in a CVT, I'll create one using a DVR/Variant Attributes. (Like you say) anytime a module wants to ch
  2. Hi Everyone, I (re)watched James Powell's talk at GDevCon#2 about Application Design Around SQLite. I really like this idea as I have an application with lots of data (from serial devices and software configuration) that's all needed in several areas of the application (and external applications) and his talk was a 'light-bulb' moment where I thought I could have a centralized SQLite database that all the modules could access to select / update data. He said the database could be the 'model' in the model-view-controller design pattern because the database is very fast. So you can col
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.