Database
|
This page describes database data migration. |
Minimum version required: 3.23 or higher
Create table definitions: See the documentation that accompanied your software.
Data Migration
Overview
If you have a small amount of data to enter use the Quick Submit feature found in the administrative area. The form can be customized to suit your data entry needs. If you have a large amount of data to enter then you need data migration capability. You can do this yourself, or outsource to Globalissa or to others. Following is a description of how to migrate data from your source file to a target file for use in phpYellow.Description
phpYellow is a database driven application and it requires that you match your source datafields with corresponding datafields in phpYellow, then to convert the resulting file into .csv or better, into .sql for direct import into phpYellow. You may utilize 3rd party SQL applications such as phpMyAdmin which lets you administer your MySQL database. Most host isps offer phpMyAdmin freely with your hosting account. Look for phpMyAdmin in your control panel.Data Inserts
There should be data inserts into each of these tables for each record to migrate:
define("TABLECUSTOMER", "pyd_contact");
define("TABLECATEGORY", "pyd_listing");
define("TABLECOUPONS", "pyd_coupons"); /* DO NOT CHANGE */
define("TABLEUSERNOTIFY", "pyd_user_notify"); /* DO NOT CHANGE */
Relational integrity
This describes what relational data values to insert in each table:- pyd_contact.customerid is the primary key
- pyd_listing.fkcustomerid is the same number as pyd_contact.customerid
This is used for a relational join of the contact and listing tables, for example in searches. - pyd_user_notify.fk_customerid should be the same number as pyd_contact.customerid
- pyd_coupons.ckey should be the same number as pyd_listing.ckey