User Tools

Site Tools


kb:bestpractices:codingconventions:architecture

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
kb:bestpractices:codingconventions:architecture [2026/07/30 07:41] – [Comparison] joerg.hampelkb:bestpractices:codingconventions:architecture [2026/10/06 13:17] (current) – joerg.hampel
Line 34: Line 34:
     * See [[kb:bestpractices:codingconventions:style#naming|00 Style]] for VI naming     * See [[kb:bestpractices:codingconventions:style#naming|00 Style]] for VI naming
     * See [[kb:bestpractices:codingconventions:layout-design#constant_vis|02 Layout & Design]] for VI icon design     * See [[kb:bestpractices:codingconventions:layout-design#constant_vis|02 Layout & Design]] for VI icon design
- 
-==== Database ==== 
- 
-  * Wrap each query in a separate SubVI 
-    * this allows for easy reuse 
-    * add documentation to describe the returned values 
-    * optional: convert the returned 2d-array of strings into a 1d-array of typedef'ed cluster 
-  * A DB connection is like a shared resource that cannot be used in parallel. (also true for SQLite) 
-    * use one db connection instance per consumer to avoid blocking 
  
 ==== Configuration ==== ==== Configuration ====
kb/bestpractices/codingconventions/architecture.txt · Last modified: 2026/10/06 13:17 by joerg.hampel