Changes between Version 18 and Version 19 of Internal/InventoryV3

Timestamp:

Nov 17, 2009, 11:32:36 PM (15 years ago)

Author:

ssugrim

Comment:

—

Internal/InventoryV3

@@ -1 +1 @@
 James is working on a second generation inventory script.
 
-Currently on: Merging scripts and getting motherboard serial number.
-
+Currently on: reorganising code
+
+Versions:
+
+Gather:0.87
+Writer:0.9
 
 It's plan is to be simpler and less ambitious than it's predecessor, but still respect the sql table structure ("as much as possible.") 
@@ -220 +224 @@
  * If a motherboard is not found then we insert it. 
  * should get node id from sql table matching against location
+
+----
+=== 11/17/09 ===
+
+Modifications on writer have been completed (preliminary checks worked). 
+ * reverted Db.hupdate to only update. The calling functions should decide whether to insert or update. 
+ * Mb_id nows checks against serial instead of location in the Identify class
+ * update_mb now checks for mb_id. If the ID is present it will update the record
+   otherwise it will insert WITHOUT specifying and ID since SQL should autoincremt the ids
+ * Nodes are uniquely identified by a triple of (node_id, location_id, motherboar_id). Its assumed that the (node_id,location_id)
+   portion is constant. Thus the only change/ update we should check for and preform is to ensure that the motherboard id matches
+   for a given node_id, location_id pair. the update_node function only modifies motherboard_id's
+
+Things that need to be done:
+ * move all the "checks" into the get methods (depreciate the get methods). check() should simply call the sub_check methods and retain
+   a hash of matches for specific data structures (table entries).
+ * update can then iterate that hash and call the respective update functions for each give table.
+ * the data structure design paradigm should be to have one data structure for each table that needs to be checked / update. It's 
+   pretty close to this, but needs a little work.
+