It's meant to hold the source of the customer in terms of where they
heard about your service, advertisement, etc.  There is a source
report that can produce a total for each source that uses that field.
If that doesn't matter right now you could use it to hold a temporary
value.

I think I would just add new fields to the end of the table or if
there are a bunch of them make a new table and put those values in
there with the account number as a key.

Paul

On Mon, Jan 23, 2012 at 5:20 PM, Bill Harris <bhar...@texoma.net> wrote:
> Paul,
>
> What is the "source" column used for?  Can I use it
> to hold a temporary value?
>
> Bill
>
> mysql> describe customer;
> +--------------------------+------------------+------+-----+------------+----------------+
> | Field                    | Type             | Null | Key | Default    | 
> Extra          |
> +--------------------------+------------------+------+-----+------------+----------------+
> *| source                   | varchar(100)     | YES  |     | NULL       *|   
>              |
> | signup_date              | date             | NO   |     | 0000-00-00 |     
>            |
> | name                     | varchar(255)     | NO   |     |            |     
>            |
> | company                  | varchar(255)     | YES  |     | NULL       |     
>            |
> | street                   | varchar(255)     | NO   |     |            |     
>            |
> | city                     | varchar(255)     | NO   |     |            |     
>            |
> | state                    | char(3)          | NO   |     |            |     
>            |
> | country                  | varchar(255)     | NO   |     | USA        |     
>            |
> | zip                      | varchar(20)      | NO   |     |            |     
>            |
> | phone                    | varchar(20)      | NO   |     |            |     
>            |
> | alt_phone                | varchar(20)      | YES  |     | NULL       |     
>            |
> | fax                      | varchar(20)      | YES  |     | NULL       |     
>            |
> | contact_email            | varchar(255)     | YES  |     | NULL       |     
>            |
> | account_number           | int(11)          | NO   | PRI | NULL       | 
> auto_increment |
> | secret_question          | varchar(254)     | YES  |     | NULL       |     
>            |
> | secret_answer            | varchar(100)     | YES  |     | NULL       |     
>            |
> | cancel_date              | date             | YES  |     | NULL       |     
>            |
> | removal_date             | date             | YES  |     | NULL       |     
>            |
> | default_billing_id       | int(10) unsigned | NO   |     | 0          |     
>            |
> | account_manager_password | varchar(60)      | YES  |     | NULL       |     
>            |
> | cancel_reason            | int(11)          | YES  |     | NULL       |     
>            |
> | notes                    | text             | YES  |     | NULL       |     
>            |
> +--------------------------+------------------+------+-----+------------+----------------+
> 22 rows in set (0.00 sec)
>
>
> On 1/23/2012 7:53 AM, Paul Yasi wrote:
>> I don't think it would break anything.
>>
>> Paul
>>
>> On Mon, Jan 23, 2012 at 8:29 AM, Bill Harris <bhar...@texoma.net> wrote:
>>> Paul,
>>>
>>> Our current "homegrown" Access-based system stores the account
>>> name as the account number (legacy from dial-up days)..
>>>
>>> I want to import the customers today, but wondered if I could add
>>> a varchar column to store the login id into (just temporarily) until
>>> I build the services up.  I was tempted to just store it in the comment
>>> field, but I have a field of those to import as well.
>>>
>>> Will adding a field at the end of the customer table break anything, 
>>> functionally?
>>>
>>> Bill
>>> ------------------------------------------------------------------------------
>>> Try before you buy = See our experts in action!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-dev2
>>> _______________________________________________
>>> Citrusdb-users mailing list
>>> Citrusdb-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/citrusdb-users
>>
>>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Citrusdb-users mailing list
> Citrusdb-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/citrusdb-users



-- 
The CitrusDB Project | http://www.citrusdb.org
Open Source Customer Care & Billing System

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Citrusdb-users mailing list
Citrusdb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/citrusdb-users

Reply via email to