Changeset - 216b4e04ca43
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2013-11-15 17:04:53
bkuhn@ebb.org
StorageAPI and ReadingAPI use case evaluation.
1 file changed with 9 insertions and 1 deletions:
0 comments (0 inline, 0 general)
ExistingProjects/Frontaccounting.mdwn
Show inline comments
...
 
@@ -90,9 +90,17 @@ restrict a user to a specific Dimension.
 
- [[Purchase Order required|UseCases/WorkFlow#purchase-order-required]] ?
 
  Seems that way.
 

	
 
# Evaluation of the [[Reading and Reporting API|UseCases/ReadingAPI]]
 

	
 
Interaction with the data seems to happen with embedded SQL statements
 
intermixed with PHP code.
 
intermixed with PHP code.  Thus, writing SQL statements is really the only
 
way to interact with the data, and as such, given that there isn't anything
 
specifically innovative about the data model, this is no better nor worse
 
than most other projects of this nature.
 

	
 
# Evaluation of the [[Storage API|UseCases/StorageAPI]]
 

	
 
Again, SQL appears to be the only way to interact with the storage of
 
double-entry data.  Double-entry data does not appear to be segmented away
 
from the other information.
 

	
0 comments (0 inline, 0 general)