Opened 11 years ago

Closed 11 years ago

#352 closed improve feature (fixed)

Adding redudant fields in memberstrads to manage orphan records

Reported by: jeanyves Owned by: jeanyves
Priority: major Milestone: 0.6-short - full copy release
Component: unknown Keywords: memberstrads
Cc: lemon-head, jeanyves


There is currently no easy way to know if a memberstrads records is really used by some other table. I want to introduce two new fields : IdRecord? and TableColumn?

TableColumn? will define the table and the column point to the current memberstrads record IdRecord? will define the # of the record in this external table

For example if members.ProfileSummary? as the value 200 for the record 68 we will have : TableColumn? with the value : "members.ProfileSummary?" and IdRecord? with the value 68

I will make a script to populate this with values and then, to be able to see which values are orphan records

The same will be done for crypted fields

Change History (9)

comment:1 Changed 11 years ago by jeanyves

  • freq_reported set to 1
  • show_on_bw set to 0

Signup now use these new fields in Alpha via (NewInsertInMTrad and NewInsertInCrypted?)

Remaining files to process are :

  • groups.php
  • myphotos.php
  • myrelations.php
  • editprofile.php
  • updatemandatory.php
  • adminmandatory.php

comment:2 Changed 11 years ago by jeanyves

  • follow_up changed from none to test on alpha

I have moved it in alpha

comment:3 Changed 11 years ago by lemon-head

I don't get exactly what this is about (I was set to cc).

Looks like the following changesets relate to this ticket:

comment:4 Changed 11 years ago by feuerdaemon

  • Cc jeanyves added

What's to test here?

comment:5 Changed 11 years ago by lemon-head

I would propose some heavy restructuring on the memberstrads and members table.

See MemberstradsTable

comment:6 Changed 11 years ago by philipp

  • Cc steinwinde removed

what is the status here? back to test? deprecated? which code changes belong to this ticket, are they on alpha or trunk?

comment:7 Changed 11 years ago by philipp

  • Milestone changed from unassigned to 0.6-short - full copy release

if there is some code for this on alpha it needs testing, otherwise we will care about this later

comment:8 Changed 11 years ago by jeanyves

  • Status changed from new to assigned

The redudant fields have been added in the database. They are just passive fields. I have filled them with a script to detect several anomalies which have been fixed.

The Alpha routines which updates memberstrads also update these fields since at least one month. In case an update was not done of one of these field this will not have any consequence (except that it will be possible to use these fields to detect an anomaly).

In conclusion : this is not a problem at all

comment:9 Changed 11 years ago by philipp

  • follow_up changed from test on alpha to none
  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.