sample records storage organization

Bug #1449787 reported by Alex
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
queXS
Fix Released
High
Alex

Bug Description

Now this is serious...

While getting deeper and deeper with backend development, faced not optimal db tables organization.
Decided to combine related bugs in one record. So..

In case of a mistake during sample import process, no other solution but to import this sample again as a new one, because:
 - It's not possible to edit sample_var name
 - It's not possible to re-define sample_var type

After sample_var's 'de-identification' relevant records still reside in 'sample' table with phone nr , Time Zone and id records.
Due to this there're some miscalculations in results/total sample values.

What for 'primary phone' records are duplicated in 'sample_var' and 'sample' tables?

And for desert: - deleting samples doesn't lead to db inconsistance if 'auto increment' is ON for sample_id string.
As for results - there're a lot of required information stored in 'case', call, call_attempt tables to querry from.

will inform on how changes are going.

To be continued...

ALex

Related branches

Alex (ddrmoscow)
Changed in quexs:
status: New → In Progress
Revision history for this message
Alex (ddrmoscow) wrote :

Hi,
seems that the case solved, required changes done, will upload to "Features" branch now,

3 in one page - set operator viewing permision / edit sample_var / delete sample-var
NOW possible to rename sample_variables, assign required variable type , delete old samples...

 Pls BE VERY CAREFULL when updating and DO NOT FORGET TO BACKUP your working installation and DB before update!

now it's a good point to decicde
   if deleting of old cases ia also required (togeter with samples or separate)...
  if additional check is required for proper var type setting/changes and mandatory var types count and check

GOOD Luck!
Have fun

Alex (ddrmoscow)
Changed in quexs:
status: In Progress → Fix Committed
assignee: nobody → Alex (ddrmoscow)
Adam Zammit (adamzammit)
Changed in quexs:
milestone: none → 1.13.0
importance: Undecided → High
Adam Zammit (adamzammit)
Changed in quexs:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.