mysql - System for tracking changes in whois records -


The best storage mechanism for a system (system to use to store the database and all records) Is Whois designed to track record changes? The program will be run once a day and a track should be kept, which was the previous value and what is the new value.

Tip data on ideas about how to store databases and different records / fields is not unnecessary / duplicate


(Added) To store data My thoughts on the system

Example One person showed "sample.com" to a person from a person's list on 1/2/2010

  Table_DomainNames DomainId | DomainName 1 example.com 2 sample.com TableContactTrack Domain ID Date time Registrar id | Registrar ID | (Others) 2 1/1/2009 1 1 2 1/1/2010 2 2 Table_ Registrar Registrar ID | RegistrarName 1 GoDaddy 2 1 and 1 Table_ Registrar Registrar ID | Registrant name 1 person 2 person b  

All tables are "app-ups only". Does this model understand? Table_ChangeTrack should be "added only" when there is a change in the observed areas.

Is there any way to make it more efficient / harder than size?

The existence or change of the primary figure whois record shows that your primary table is:

  & lt; ID, domain, effective_date, description_id & gt;  

Where real_itiss data points to actual individuals, it is probably normalized:

   

But note that most registrars consider the information their property (whether it is or not) and likes warnings:

Use Conditions: You are not authorized to access or inquire into our Whise database through the use of electronic processes which are high amounts and automatic, to register domain names or modify existing registration Area is required as necessary to ...

If you can expect to read too much your database they will bite you.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -