Abstract: Apparatus and method for a physical store to associate a mobile device identity with a customer's membership card ID. A non-intrusive solution automatically builds a link between the identified device d and a recorded transaction associated with a membership card ID. The method builds a device visiting journey trajectory for a device d from data recording the physical movement of that device d obtained from an in-store locating system, and Points of Interest data information. There is further built from purchase transaction data and data representing a physical store layout, a member's procurement journey. A membership matching engine analyzes the spatio-temporal occurrences and sequences used to build up the feasible link and their binding possibility. In addition, the system can also use historical data and update the linkage and binding possibility adaptively. The system automatically detects the membership card and device matching without asking customer to perform the binding manually.

Abstract: Provided is a database schema migration difference detecting technique for detecting differences of a customized database schema before and after database migration by using XML technology, including: extracting a first database schema from a fresh database of a release and saving the first database schema in a first XML file; extracting a customized database schema from a customized database of the release and saving the customized database schema in a second XML file; comparing the first and second XML files, filtering the identical content in the first and second XML files and saving differences in a delta XML file; and comparing the delta XML file with a new database to detect a state of the customized database schema after migration. The detecting state indicates whether there is any loss or change in the customized database schema after migration, as well as, conflicts with the database schema in a database of a new release.

Abstract: Provided is a database schema migration difference detecting technique for detecting differences of a customized database schema before and after database migration by using XML technology, including: extracting a first database schema from a fresh database of a release and saving the first database schema in a first XML file; extracting a customized database schema from a customized database of the release and saving the customized database schema in a second XML file; comparing the first and second XML files, filtering the identical content in the first and second XML files and saving differences in a delta XML file; and comparing the delta XML file with a new database to detect a state of the customized database schema after migration. The detecting state indicates whether there is any loss or change in the customized database schema after migration, as well as, conflicts with the database schema in a database of a new release.

Abstract: Provided is a database schema migration difference detecting technique for detecting differences of a customized database schema before and after database migration by using XML technology, including: extracting a first database schema from a fresh database of a release and saving the first database schema in a first XML file; extracting a customized database schema from a customized database of the release and saving the customized database schema in a second XML file; comparing the first and second XML files, filtering the identical content in the first and second XML files and saving differences in a delta XML file; and comparing the delta XML file with a new database to detect a state of the customized database schema after migration. The detecting state indicates whether there is any loss or change in the customized database schema after migration, as well as, conflicts with the database schema in a database of a new release.