chasers-general — General CHASERS list traffic

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Ok, that seems to have fixed that, but we're back with the housing unit =
issue, for some reason.
=20
I can add a housing unit, such as MEN1 or MEN2 (the designation for the =
men's program we created) but when you go to add a Compass Center =
Residence to a client record, the unit drop down is still blank. Under =
Housing, further strangeness is occuring, since there now seems to be =
two places to enter housing units. Here's what the page looks like:
=20

Housing Unit Maintenance

show empty recordshide empty records


No Housing Units

(Add a Housing Unit)=20

No Housing Unit Subsidies

(Add a Housing Unit Subsidy)=20

  <javascript:showHideElement('housing_unitChildListAll')>   =20

Browse ALL Housing Unit records

Back to top=20
Add a Housing Unit
=09
Records 1-2 (of 2 total records)
Sorted by Unit
Page 1 of 1
 	 #	 Unit=09
Date=09
Date End=09
Unit Type=09
Unit Size=09
Project=09
View
1	 MEN	 12/12/2006	 12/12/2008	 Other or N/A	  	 Mens Program=09
View
2	 MEN2	 12/12/2006	 12/12/2007	 Other or N/A	  	 Mens Program=09
Page 1 of 1

Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...
=20

________________________________

From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Tue 12/12/2006 9:32 AM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS




Nicholas Burmeister wrote:
> Ok, I made those changes (and noticed that we had previously entered =
those same lines below housing, so I removed those) and there's still =
something funky going on. The script runs to nearly the end, and then =
pops this out:
>
> psql:install.sql:230: ERROR:  syntax error at or near "psql" at =
character 1393
> psql:install.sql:230: LINE 41: */psql:create.tbl_log.sql:38: ERROR:  =
function post_log_refe...
> psql:install.sql:230:
> CompassCenterTest=3D>
>
> =20
You've somehow ended up with error messages _in_ your install.sql
script, see below.
> Below my sig I will include the entirety of install.sql. Have a look =
at it, especially that odd line I mentioned before. I'm also concerned =
that its not doing rollback, simply creating the db in a broken state. =
This is a bit of a pain since I forget the text command to drop the =
database and I have to go into webmin to drop the db. Can you refresh my =
memory, or perhaps see how come the database creation isn't rolling back =
when it fails?
> =20
# su postgres
# dropdb {database name}
>
> Nicholas Burmeister
> IT Department
> The Compass Center
> 206-357-3144
> nbu...@co...
>
> /*
>  *
>  * This script should be run through the psql interface, as it makes =
heavy use
>  * of the \i command to run sub-scripts
>  *
>  * IMPORTANT NOTES:
>  *
>  *   * install.db.sql needs to be run before this script
>  *
>  *   * CHASERS requires all elements of this script up to the "Child =
Records" section
>  *
>  *   * Don't forget to edit add.initial_user.sql to create the basic =
CHASERS admin user
>  */
>
> /* to ensure a complete database,
>  * the install is run within a transaction,
>  * however, if this becomes un-manageable, comment out
>  * this line:
>  */
> BEGIN;
> /****/
>
>
> /************************
>  *        staff         *
>  ************************/
>
> /* basic lookups */
> /*
>  * NOTE: these create scripts generally insert data, so edit them =
prior to installation for
>  * custom values.
>  */
>
> \i create.l_desc_position.sql            /* staff positions */
> \i create.l_desc_facility.sql            /* buildings and physical =
locations */
> \i create.l_desc_shift.sql
> \i create.l_desc_staff_type.sql
> \i create.l_desc_employment_status.sql
> \i create.l_desc_program.sql           =20
> \i create.l_desc_project.sql
> \i create.l_gender.sql
> \i create.l_accuracy.sql                 /* data accuracy flag -- used =
by many tables */
> \i create.l_yes_no.sql
>
> \i create.tbl_staff.sql
> \i create.tbl_user_option.sql
> \i create.tbl_staff_password.sql
> \i create.tbl_staff_employment.sql
> \i create.view.staff.sql
>
> \i create.l_permission_type.sql
> \i create.tbl_permission.sql
>
> /* alerts */
> \i functions/create.alert_notify.sql
> \i create.l_alert_notify_action.sql
> \i create.tbl_alert.sql
> \i create.tbl_alert_notify.sql
> \i create.view.alert_consolidated.sql
> \i create.view.alert_notify_enabled_objects.sql
>
> /* unduplication capability */
> \i create.tbl_duplication_staff.sql
> /**********************IMPORTANT**********************\
>  *                                                   *
>  *  This file should be modified as it creates the   *
>  *  admin and system users (and passwords)           *
>  *                                                   *
> \*****************************************************/
> \i add.initial_user.sql
>
> /* must be created after sys_user() function is created */
> \i create.tbl_user_login.sql
>
> /*********************************************
>  *    Core CHASERS Tables and functions      *
>  *********************************************/
>
>
> /* db_revision_history */
>
> \i create.db_revision_history.sql
>
> INSERT INTO db_revision_history
>        VALUES ('Initial CHASERS =
Install','',CURRENT_TIMESTAMP,sys_user(),'Initial Install','');
>
> /* known db list */
> \i create.db_list.sql
>
> INSERT INTO db_list
>       VALUES (current_database(),
>       'CHASERS'/* description */,
>       FALSE    /* test db? */,
>       ''       /* primary url */
>       );
>
> /* if there will be a dedicated test db, enter an additional record */
> /* INSERT INTO db_list
>       VALUES (current_database()||'_test',
>       'CHASERS Test DB',
>       TRUE,
>       ''
>       );
> */
>
> \i create.tbl_engine_config.sql
>
> \i create.tbl_help.sql
> \i create.view.db_chasers_relations.sql
> \i create.view.db_chasers_functions.sql
>
> /* core functions */
>
> \i functions/create.functions_array.sql
> \i functions/create.rank_client_search_results.sql
> \i functions/create.functions_changed_at_trigger.sql
>
> /* log */
> \i functions/create.functions_log.sql
> \i create.tbl_reference.sql
> \i create.tbl_log.sql /* modify this for appropriate log groups */
>
> /* feedback */
> /*
> \i create.tbl_feedback.sql
> */
>
> /**********************************************************\
>  *                         Client                         *
>  *                                                        *
>  * Structure this table as desired. It will servce as the *
>  * key 'parent' record for all subsequent 'child'         *
>  * records.                                               *
> \**********************************************************/
>
> /* basic lookups */
> \i create.l_ethnicity.sql
> \i create.l_language.sql
> \i create.l_veteran_status.sql
> \i create.l_name_suffix.sql
> \i create.l_staff_assign_type.sql
> \i create.l_agency.sql
>
> \i create.tbl_client.sql
> \i create.tbl_client_protected.sql
> \i create.view.client.sql
> \i create.tbl_client_ref.sql
>
> \i create.tbl_staff_assign.sql
>
> /* additional core functions referencing client and staff */
> \i functions/create.functions.sql
>
> /* unduplication capability */
> \i create.tbl_duplication.sql
>
> /**********************************************************\
>  *                       Child Records                    *
>  *                                                        *
>  * At this point, the most basic install is complete.     *
>  * Staff and Client child records can now be added.       *
>  *                                                        *
> \**********************************************************/
> \i create.l_exit_status.sql  /* used by housing and CD */
>
> \i create.l_disability.sql
> \i create.tbl_disability.sql
>
> \i create.tbl_client_note.sql
>
> /* Client Death */
> \i create.l_client_death_data_source.sql
> \i create.l_client_death_location.sql
> \i create.l_client_death_type.sql
> \i create.tbl_client_death.sql
>
> /* Added by Nick - Employment Status */
> \i create.l_employment_application_status.sql
> \i create.l_employment_level.sql
> \i create.l_employment_termination.sql
> \i create.l_employment_status.sql
> \i create.tbl_employment_status.sql
>
>
>
> /* BAR SYSTEM */
> /*
> \i create.l_bar_location.sql
> \i create.l_brc_resolution.sql
>
> \i create.tbl_bar.sql
> \i create.view.bar.sql
> */psql:create.tbl_log.sql:38: ERROR:  function post_log_references() =
does not exist
> psql:install.sql:111: \i: extra argument "/*" ignored
>
> =20
the above 2 lines shouldn't be there
> /* SHELTER-SPECIFIC TABLES */
> /*
> \i install.shelter.sql
> */
>
> /* MAIL SYSTEM */
> /*
> \i create.l_mail_type.sql
> \i create.l_mail_delivery.sql
>
> \i create.tbl_mail.sql
> */
>
>
> /* HOUSING-SPECIFIC TABLES */
> \i install.housing.sql
> /* Added by Nick - cd */
> /* \i create.l_service.sql */
> \i create.l_referral.sql
> \i create.l_progress.sql
> \i create.view.l_service_cd.sql
> \i create.view.service_cd.sql
> \i create.tbl_cd_reg.sql
>
>
>
>
> /* CALENDAR SYSTEM */
>
> \i install.calendar.sql
>
>
>
> COMMIT;
>
> =20
-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Ok, I made those changes (and noticed that we had previously entered those same lines below housing, so I removed those) and there's still something funky going on. The script runs to nearly the end, and then pops this out:
>
> psql:install.sql:230: ERROR:  syntax error at or near "psql" at character 1393
> psql:install.sql:230: LINE 41: */psql:create.tbl_log.sql:38: ERROR:  function post_log_refe...
> psql:install.sql:230: 
> CompassCenterTest=>
>
>   
You've somehow ended up with error messages _in_ your install.sql
script, see below.
> Below my sig I will include the entirety of install.sql. Have a look at it, especially that odd line I mentioned before. I'm also concerned that its not doing rollback, simply creating the db in a broken state. This is a bit of a pain since I forget the text command to drop the database and I have to go into webmin to drop the db. Can you refresh my memory, or perhaps see how come the database creation isn't rolling back when it fails?
>   
# su postgres
# dropdb {database name}
>
> Nicholas Burmeister
> IT Department
> The Compass Center
> 206-357-3144
> nbu...@co...
>
> /*
>  * 
>  * This script should be run through the psql interface, as it makes heavy use
>  * of the \i command to run sub-scripts
>  *
>  * IMPORTANT NOTES: 
>  *
>  *   * install.db.sql needs to be run before this script
>  *
>  *   * CHASERS requires all elements of this script up to the "Child Records" section
>  *
>  *   * Don't forget to edit add.initial_user.sql to create the basic CHASERS admin user
>  */
>
> /* to ensure a complete database, 
>  * the install is run within a transaction,
>  * however, if this becomes un-manageable, comment out 
>  * this line:
>  */
> BEGIN; 
> /****/
>
>
> /************************
>  *        staff         *
>  ************************/
>
> /* basic lookups */
> /* 
>  * NOTE: these create scripts generally insert data, so edit them prior to installation for
>  * custom values.
>  */
>
> \i create.l_desc_position.sql            /* staff positions */
> \i create.l_desc_facility.sql            /* buildings and physical locations */
> \i create.l_desc_shift.sql
> \i create.l_desc_staff_type.sql
> \i create.l_desc_employment_status.sql
> \i create.l_desc_program.sql             
> \i create.l_desc_project.sql
> \i create.l_gender.sql
> \i create.l_accuracy.sql                 /* data accuracy flag -- used by many tables */
> \i create.l_yes_no.sql
>
> \i create.tbl_staff.sql
> \i create.tbl_user_option.sql
> \i create.tbl_staff_password.sql
> \i create.tbl_staff_employment.sql
> \i create.view.staff.sql
>
> \i create.l_permission_type.sql
> \i create.tbl_permission.sql
>
> /* alerts */
> \i functions/create.alert_notify.sql
> \i create.l_alert_notify_action.sql
> \i create.tbl_alert.sql
> \i create.tbl_alert_notify.sql
> \i create.view.alert_consolidated.sql
> \i create.view.alert_notify_enabled_objects.sql
>
> /* unduplication capability */
> \i create.tbl_duplication_staff.sql
> /**********************IMPORTANT**********************\
>  *                                                   *
>  *  This file should be modified as it creates the   *
>  *  admin and system users (and passwords)           *
>  *                                                   *
> \*****************************************************/
> \i add.initial_user.sql
>
> /* must be created after sys_user() function is created */
> \i create.tbl_user_login.sql
>
> /*********************************************
>  *    Core CHASERS Tables and functions      *
>  *********************************************/
>
>
> /* db_revision_history */
>
> \i create.db_revision_history.sql
>
> INSERT INTO db_revision_history 
> 	 VALUES ('Initial CHASERS Install','',CURRENT_TIMESTAMP,sys_user(),'Initial Install','');
>
> /* known db list */
> \i create.db_list.sql
>
> INSERT INTO db_list
> 	VALUES (current_database(),
> 	'CHASERS'/* description */,
> 	FALSE    /* test db? */,
> 	''       /* primary url */
> 	);
>
> /* if there will be a dedicated test db, enter an additional record */
> /* INSERT INTO db_list
> 	VALUES (current_database()||'_test',
> 	'CHASERS Test DB',
> 	TRUE,
> 	''
> 	);
> */
>
> \i create.tbl_engine_config.sql
>
> \i create.tbl_help.sql
> \i create.view.db_chasers_relations.sql
> \i create.view.db_chasers_functions.sql
>
> /* core functions */
>
> \i functions/create.functions_array.sql
> \i functions/create.rank_client_search_results.sql
> \i functions/create.functions_changed_at_trigger.sql
>
> /* log */
> \i functions/create.functions_log.sql
> \i create.tbl_reference.sql
> \i create.tbl_log.sql /* modify this for appropriate log groups */
>
> /* feedback */
> /*
> \i create.tbl_feedback.sql
> */
>
> /**********************************************************\
>  *                         Client                         *
>  *                                                        *
>  * Structure this table as desired. It will servce as the *
>  * key 'parent' record for all subsequent 'child'         *
>  * records.                                               *
> \**********************************************************/
>
> /* basic lookups */
> \i create.l_ethnicity.sql
> \i create.l_language.sql
> \i create.l_veteran_status.sql
> \i create.l_name_suffix.sql
> \i create.l_staff_assign_type.sql
> \i create.l_agency.sql
>
> \i create.tbl_client.sql
> \i create.tbl_client_protected.sql
> \i create.view.client.sql
> \i create.tbl_client_ref.sql
>
> \i create.tbl_staff_assign.sql
>
> /* additional core functions referencing client and staff */
> \i functions/create.functions.sql
>
> /* unduplication capability */
> \i create.tbl_duplication.sql
>
> /**********************************************************\
>  *                       Child Records                    *
>  *                                                        *
>  * At this point, the most basic install is complete.     *
>  * Staff and Client child records can now be added.       *
>  *                                                        *
> \**********************************************************/
> \i create.l_exit_status.sql  /* used by housing and CD */
>
> \i create.l_disability.sql
> \i create.tbl_disability.sql
>
> \i create.tbl_client_note.sql
>
> /* Client Death */
> \i create.l_client_death_data_source.sql
> \i create.l_client_death_location.sql
> \i create.l_client_death_type.sql
> \i create.tbl_client_death.sql
>
> /* Added by Nick - Employment Status */
> \i create.l_employment_application_status.sql
> \i create.l_employment_level.sql
> \i create.l_employment_termination.sql
> \i create.l_employment_status.sql
> \i create.tbl_employment_status.sql
>
>
>
> /* BAR SYSTEM */
> /*
> \i create.l_bar_location.sql
> \i create.l_brc_resolution.sql
>
> \i create.tbl_bar.sql
> \i create.view.bar.sql
> */psql:create.tbl_log.sql:38: ERROR:  function post_log_references() does not exist
> psql:install.sql:111: \i: extra argument "/*" ignored
>
>   
the above 2 lines shouldn't be there
> /* SHELTER-SPECIFIC TABLES */
> /*
> \i install.shelter.sql
> */
>
> /* MAIL SYSTEM */
> /*
> \i create.l_mail_type.sql
> \i create.l_mail_delivery.sql
>
> \i create.tbl_mail.sql
> */
>
>
> /* HOUSING-SPECIFIC TABLES */
> \i install.housing.sql
> /* Added by Nick - cd */
> /* \i create.l_service.sql */
> \i create.l_referral.sql
> \i create.l_progress.sql
> \i create.view.l_service_cd.sql
> \i create.view.service_cd.sql
> \i create.tbl_cd_reg.sql 
>
>
>
>
> /* CALENDAR SYSTEM */
>
> \i install.calendar.sql
>
>
>
> COMMIT;
>
>   
-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Ok, I made those changes (and noticed that we had previously entered =
those same lines below housing, so I removed those) and there's still =
something funky going on. The script runs to nearly the end, and then =
pops this out:

psql:install.sql:230: ERROR:  syntax error at or near "psql" at =
character 1393
psql:install.sql:230: LINE 41: */psql:create.tbl_log.sql:38: ERROR:  =
function post_log_refe...
psql:install.sql:230:=20
CompassCenterTest=3D>

Below my sig I will include the entirety of install.sql. Have a look at =
it, especially that odd line I mentioned before. I'm also concerned that =
its not doing rollback, simply creating the db in a broken state. This =
is a bit of a pain since I forget the text command to drop the database =
and I have to go into webmin to drop the db. Can you refresh my memory, =
or perhaps see how come the database creation isn't rolling back when it =
fails?


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...

/*
 *=20
 * This script should be run through the psql interface, as it makes =
heavy use
 * of the \i command to run sub-scripts
 *
 * IMPORTANT NOTES:=20
 *
 *   * install.db.sql needs to be run before this script
 *
 *   * CHASERS requires all elements of this script up to the "Child =
Records" section
 *
 *   * Don't forget to edit add.initial_user.sql to create the basic =
CHASERS admin user
 */

/* to ensure a complete database,=20
 * the install is run within a transaction,
 * however, if this becomes un-manageable, comment out=20
 * this line:
 */
BEGIN;=20
/****/


/************************
 *        staff         *
 ************************/

/* basic lookups */
/*=20
 * NOTE: these create scripts generally insert data, so edit them prior =
to installation for
 * custom values.
 */

\i create.l_desc_position.sql            /* staff positions */
\i create.l_desc_facility.sql            /* buildings and physical =
locations */
\i create.l_desc_shift.sql
\i create.l_desc_staff_type.sql
\i create.l_desc_employment_status.sql
\i create.l_desc_program.sql            =20
\i create.l_desc_project.sql
\i create.l_gender.sql
\i create.l_accuracy.sql                 /* data accuracy flag -- used =
by many tables */
\i create.l_yes_no.sql

\i create.tbl_staff.sql
\i create.tbl_user_option.sql
\i create.tbl_staff_password.sql
\i create.tbl_staff_employment.sql
\i create.view.staff.sql

\i create.l_permission_type.sql
\i create.tbl_permission.sql

/* alerts */
\i functions/create.alert_notify.sql
\i create.l_alert_notify_action.sql
\i create.tbl_alert.sql
\i create.tbl_alert_notify.sql
\i create.view.alert_consolidated.sql
\i create.view.alert_notify_enabled_objects.sql

/* unduplication capability */
\i create.tbl_duplication_staff.sql
/**********************IMPORTANT**********************\
 *                                                   *
 *  This file should be modified as it creates the   *
 *  admin and system users (and passwords)           *
 *                                                   *
\*****************************************************/
\i add.initial_user.sql

/* must be created after sys_user() function is created */
\i create.tbl_user_login.sql

/*********************************************
 *    Core CHASERS Tables and functions      *
 *********************************************/


/* db_revision_history */

\i create.db_revision_history.sql

INSERT INTO db_revision_history=20
	 VALUES ('Initial CHASERS =
Install','',CURRENT_TIMESTAMP,sys_user(),'Initial Install','');

/* known db list */
\i create.db_list.sql

INSERT INTO db_list
	VALUES (current_database(),
	'CHASERS'/* description */,
	FALSE    /* test db? */,
	''       /* primary url */
	);

/* if there will be a dedicated test db, enter an additional record */
/* INSERT INTO db_list
	VALUES (current_database()||'_test',
	'CHASERS Test DB',
	TRUE,
	''
	);
*/

\i create.tbl_engine_config.sql

\i create.tbl_help.sql
\i create.view.db_chasers_relations.sql
\i create.view.db_chasers_functions.sql

/* core functions */

\i functions/create.functions_array.sql
\i functions/create.rank_client_search_results.sql
\i functions/create.functions_changed_at_trigger.sql

/* log */
\i functions/create.functions_log.sql
\i create.tbl_reference.sql
\i create.tbl_log.sql /* modify this for appropriate log groups */

/* feedback */
/*
\i create.tbl_feedback.sql
*/

/**********************************************************\
 *                         Client                         *
 *                                                        *
 * Structure this table as desired. It will servce as the *
 * key 'parent' record for all subsequent 'child'         *
 * records.                                               *
\**********************************************************/

/* basic lookups */
\i create.l_ethnicity.sql
\i create.l_language.sql
\i create.l_veteran_status.sql
\i create.l_name_suffix.sql
\i create.l_staff_assign_type.sql
\i create.l_agency.sql

\i create.tbl_client.sql
\i create.tbl_client_protected.sql
\i create.view.client.sql
\i create.tbl_client_ref.sql

\i create.tbl_staff_assign.sql

/* additional core functions referencing client and staff */
\i functions/create.functions.sql

/* unduplication capability */
\i create.tbl_duplication.sql

/**********************************************************\
 *                       Child Records                    *
 *                                                        *
 * At this point, the most basic install is complete.     *
 * Staff and Client child records can now be added.       *
 *                                                        *
\**********************************************************/
\i create.l_exit_status.sql  /* used by housing and CD */

\i create.l_disability.sql
\i create.tbl_disability.sql

\i create.tbl_client_note.sql

/* Client Death */
\i create.l_client_death_data_source.sql
\i create.l_client_death_location.sql
\i create.l_client_death_type.sql
\i create.tbl_client_death.sql

/* Added by Nick - Employment Status */
\i create.l_employment_application_status.sql
\i create.l_employment_level.sql
\i create.l_employment_termination.sql
\i create.l_employment_status.sql
\i create.tbl_employment_status.sql



/* BAR SYSTEM */
/*
\i create.l_bar_location.sql
\i create.l_brc_resolution.sql

\i create.tbl_bar.sql
\i create.view.bar.sql
*/psql:create.tbl_log.sql:38: ERROR:  function post_log_references() =
does not exist
psql:install.sql:111: \i: extra argument "/*" ignored


/* SHELTER-SPECIFIC TABLES */
/*
\i install.shelter.sql
*/

/* MAIL SYSTEM */
/*
\i create.l_mail_type.sql
\i create.l_mail_delivery.sql

\i create.tbl_mail.sql
*/


/* HOUSING-SPECIFIC TABLES */
\i install.housing.sql
/* Added by Nick - cd */
/* \i create.l_service.sql */
\i create.l_referral.sql
\i create.l_progress.sql
\i create.view.l_service_cd.sql
\i create.view.service_cd.sql
\i create.tbl_cd_reg.sql=20




/* CALENDAR SYSTEM */

\i install.calendar.sql



COMMIT;

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Hi Jon,
>
> Things here didn't work out as planned. I entered the new install entries into install.sql as so:
>
>
> \i create.tbl_reference.sql
> \i create.tbl_log.sql /* modify this for appropriate log groups */
>
> \i create.view.db_chasers_relations.sql
> \i create.view.db_chasers_functions.sql
>
> /* core functions */
>
> \i functions/create.functions_array.sql
> \i functions/create.rank_client_search_results.sql
> \i functions/create.functions_changed_at_trigger.sql
> \i functions/create.functions_log.sql
>
>   
That was my mistake. Please change your install.sql to look like this:
/* core functions */

\i functions/create.functions_array.sql
\i functions/create.rank_client_search_results.sql
\i functions/create.functions_changed_at_trigger.sql

/* log */
\i functions/create.functions_log.sql
\i create.tbl_reference.sql
\i create.tbl_log.sql /* modify this for appropriate log groups */

(The reason this didn't work is I got the order wrong before). I've
updated the code so that future versions will have this right.

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Hi Jon,

Things here didn't work out as planned. I entered the new install =
entries into install.sql as so:


\i create.tbl_reference.sql
\i create.tbl_log.sql /* modify this for appropriate log groups */

\i create.view.db_chasers_relations.sql
\i create.view.db_chasers_functions.sql

/* core functions */

\i functions/create.functions_array.sql
\i functions/create.rank_client_search_results.sql
\i functions/create.functions_changed_at_trigger.sql
\i functions/create.functions_log.sql

I then uncommented the following lines in create.tbl_log.sql:

CREATE TRIGGER log_insert_references
	AFTER INSERT ON tbl_log FOR EACH ROW=20
	EXECUTE PROCEDURE post_log_references();

When I drop and try to reinstall the database, I get the following =
error:

psql:create.tbl_log.sql:31: NOTICE:  CREATE TABLE will create implicit =
sequence "tbl_log_log_id_seq" for serial column "tbl_log.log_id"
psql:create.tbl_log.sql:31: NOTICE:  CREATE TABLE / PRIMARY KEY will =
create implicit index "tbl_log_pkey" for table "tbl_log"
CREATE TABLE
CREATE VIEW
psql:create.tbl_log.sql:38: ERROR:  function post_log_references() does =
not exist
psql:install.sql:111: \i: extra argument "/*" ignored
psql:install.sql:111: \i: extra argument "modify" ignored
psql:install.sql:111: \i: extra argument "this" ignored
psql:install.sql:111: \i: extra argument "for" ignored
psql:install.sql:111: \i: extra argument "appropriate" ignored
psql:install.sql:111: \i: extra argument "log" ignored
psql:install.sql:111: \i: extra argument "groups" ignored
psql:install.sql:111: \i: extra argument "*/" ignored
psql:create.view.db_chasers_relations.sql:19: ERROR:  current =
transaction is aborted, commands ignored until end of transaction block
psql:create.view.db_chasers_functions.sql:54: ERROR:  current =
transaction is aborted, commands ignored until end of transaction block

and the remaining is all errors. Here's the odd part. Within instal.sql, =
I noticed an inserted bit of code that looks like so:

*/psql:create.tbl_log.sql:38: ERROR:  function post_log_references() =
does not exist
psql:install.sql:111: \i: extra argument "/*" ignored

Is this an intended insert? As in, something you wrote in?=20


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Wed 12/6/2006 3:14 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20


Nicholas Burmeister wrote:
> Oops:
>
> Also, please verify that "log" is not commented out in
> config/client_config.php
>
> That was it. I was able to post a log.=20
>
> However, now that that's done, when I go to view the log entry, and =
click on the 'subject' or the 'show the logs on 1 page' link, I get the =
data below, but not before this error message appears at the top of the =
page:
>
> Couldn't query with: SELECT log.*, staff_name(log.added_by) AS =
_added_by,
> SUBSTRING(log_text
> from 1 for 90) as Snippet
>
> FROM log
> WHERE (log_id IN (SELECT from_id
> FROM reference
> WHERE to_id =3D 1 AND to_table=3D'log')
> )
> The Postgres SQL server reported an error.
> The error text was: ERROR: relation "reference" does not exist
> The program is continuing
>
> Warning: pg_num_rows(): supplied argument is not a valid PostgreSQL =
result resource in /var/www/html/chasers/sql_layer.php on line 420
>  =20
This is a bug in install.sql.

Please add this line before \i create.tbl_log.sql:

\i create.tbl_reference.sql

Also, if you want to utilize this table (it stores references from one
log to another such that the text "log xxx" would provide a link to log
xxx and vice-versa), you should also add this line:

\i functions/create.functions_log.sql

And in create.tbl_log.sql uncomment this trigger:

CREATE TRIGGER log_insert_references
    AFTER INSERT ON tbl_log FOR EACH ROW
    EXECUTE PROCEDURE post_log_references();

This is what the relevant section of the fixed copy of install.sql now
looks like:

..snip...
\i create.tbl_reference.sql
\i create.tbl_log.sql /* modify this for appropriate log groups */

\i create.view.db_chasers_relations.sql
\i create.view.db_chasers_functions.sql

/* core functions */

\i functions/create.functions_array.sql
\i functions/create.rank_client_search_results.sql
\i functions/create.functions_changed_at_trigger.sql
\i functions/create.functions_log.sql

...snip...

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Oops:
>
> Also, please verify that "log" is not commented out in
> config/client_config.php
>
> That was it. I was able to post a log. 
>
> However, now that that's done, when I go to view the log entry, and click on the 'subject' or the 'show the logs on 1 page' link, I get the data below, but not before this error message appears at the top of the page:
>
> Couldn't query with: SELECT log.*, staff_name(log.added_by) AS _added_by,
> SUBSTRING(log_text
> from 1 for 90) as Snippet
>
> FROM log
> WHERE (log_id IN (SELECT from_id
> FROM reference
> WHERE to_id = 1 AND to_table='log')
> )
> The Postgres SQL server reported an error.
> The error text was: ERROR: relation "reference" does not exist
> The program is continuing
>
> Warning: pg_num_rows(): supplied argument is not a valid PostgreSQL result resource in /var/www/html/chasers/sql_layer.php on line 420
>   
This is a bug in install.sql.

Please add this line before \i create.tbl_log.sql:

\i create.tbl_reference.sql

Also, if you want to utilize this table (it stores references from one
log to another such that the text "log xxx" would provide a link to log
xxx and vice-versa), you should also add this line:

\i functions/create.functions_log.sql

And in create.tbl_log.sql uncomment this trigger:

CREATE TRIGGER log_insert_references
    AFTER INSERT ON tbl_log FOR EACH ROW
    EXECUTE PROCEDURE post_log_references();

This is what the relevant section of the fixed copy of install.sql now
looks like:

..snip...
\i create.tbl_reference.sql
\i create.tbl_log.sql /* modify this for appropriate log groups */

\i create.view.db_chasers_relations.sql
\i create.view.db_chasers_functions.sql

/* core functions */

\i functions/create.functions_array.sql
\i functions/create.rank_client_search_results.sql
\i functions/create.functions_changed_at_trigger.sql
\i functions/create.functions_log.sql

...snip...

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Oops:

Also, please verify that "log" is not commented out in
config/client_config.php

That was it. I was able to post a log.=20

However, now that that's done, when I go to view the log entry, and =
click on the 'subject' or the 'show the logs on 1 page' link, I get the =
data below, but not before this error message appears at the top of the =
page:

Couldn't query with: SELECT log.*, staff_name(log.added_by) AS =
_added_by,
SUBSTRING(log_text
from 1 for 90) as Snippet

FROM log
WHERE (log_id IN (SELECT from_id
FROM reference
WHERE to_id =3D 1 AND to_table=3D'log')
)
The Postgres SQL server reported an error.
The error text was: ERROR: relation "reference" does not exist
The program is continuing

Warning: pg_num_rows(): supplied argument is not a valid PostgreSQL =
result resource in /var/www/html/chasers/sql_layer.php on line 420


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Wed 12/6/2006 1:24 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Yep, I even dropped and redid the database (takes about 40 secs on my =
machine here, an old PII) Line 15, btw, I think might be referencing =
create.tbl_log.sql. Line 15 is in_cascade:
>
> 	was_drugs			BOOLEAN NOT NULL,
> 	in_shelter			BOOLEAN NOT NULL DEFAULT false,
> 	in_cascade			BOOLEAN NOT NULL DEFAULT false,
> 	in_mens			BOOLEAN NOT NULL DEFAULT false,
> 	in_vets			BOOLEAN NOT NULL DEFAULT false, =20
> 	in_clinical			BOOLEAN NOT NULL DEFAULT false,
> 	in_connections		BOOLEAN NOT NULL DEFAULT false,
>
>  =20
The actual error is at "character 15", not line. The problem is at the
INSERT INTO (... It should say INSERT INTO tbl_log (...

So CHASERS can't find the log table. What do you get if you do a "\d
tbl_log" and "\d log" from psql?

If that gives you info, what do you get from the CHASERS admin page if
you try to browse "log" and "tbl_log"?


-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Yep, I even dropped and redid the database (takes about 40 secs on my machine here, an old PII) Line 15, btw, I think might be referencing create.tbl_log.sql. Line 15 is in_cascade:
>
> 	was_drugs			BOOLEAN NOT NULL,
> 	in_shelter			BOOLEAN NOT NULL DEFAULT false,
> 	in_cascade			BOOLEAN NOT NULL DEFAULT false,
> 	in_mens			BOOLEAN NOT NULL DEFAULT false,
> 	in_vets			BOOLEAN NOT NULL DEFAULT false,  
> 	in_clinical			BOOLEAN NOT NULL DEFAULT false,
> 	in_connections		BOOLEAN NOT NULL DEFAULT false,
>
>   
The actual error is at "character 15", not line. The problem is at the
INSERT INTO (... It should say INSERT INTO tbl_log (...

So CHASERS can't find the log table. What do you get if you do a "\d
tbl_log" and "\d log" from psql?

If that gives you info, what do you get from the CHASERS admin page if
you try to browse "log" and "tbl_log"?

Also, please verify that "log" is not commented out in
config/client_config.php

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Yep, I even dropped and redid the database (takes about 40 secs on my =
machine here, an old PII) Line 15, btw, I think might be referencing =
create.tbl_log.sql. Line 15 is in_cascade:

	was_drugs			BOOLEAN NOT NULL,
	in_shelter			BOOLEAN NOT NULL DEFAULT false,
	in_cascade			BOOLEAN NOT NULL DEFAULT false,
	in_mens			BOOLEAN NOT NULL DEFAULT false,
	in_vets			BOOLEAN NOT NULL DEFAULT false, =20
	in_clinical			BOOLEAN NOT NULL DEFAULT false,
	in_connections		BOOLEAN NOT NULL DEFAULT false,


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Wed 12/6/2006 1:09 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Ok, I managed to update those two files for logs, but I think =
something was gummed up in the process, or came wonky. The fields show =
up fine in the log query screen, but when I attempt to add a log, I get =
the following error, which I regrettably cannot figure out:
>
>
> Posting log... please stand by
> Couldn't query with: INSERT INTO =
(log_text,subject,occurred_at,was_assault_staff,was_threat_staff,was_assa=
ult_client,was_spd,was_medics,was_bar,was_drugs,added_by,changed_by,in_sh=
elter,in_cascade,in_mens,in_vets,in_clinical,in_connections,added_at,md5_=
sum) VALUES ('Joe was hit by a flying banana','accident','2006-01-06 =
13:30:00','N','N','N','N','Y','N','N','2','2','f','t','f','f','f','f','20=
06-12-06 13:02:51','ee1dfe13d1dca49e5961bab7158bff1f')
> The Postgres SQL server reported an error.
> The error text was: ERROR: syntax error at or near "(" at character 15
>  =20
Did you update the engine array after making changes?

-Jonathan

-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Ok, I managed to update those two files for logs, but I think something was gummed up in the process, or came wonky. The fields show up fine in the log query screen, but when I attempt to add a log, I get the following error, which I regrettably cannot figure out:
>
>
> Posting log... please stand by
> Couldn't query with: INSERT INTO (log_text,subject,occurred_at,was_assault_staff,was_threat_staff,was_assault_client,was_spd,was_medics,was_bar,was_drugs,added_by,changed_by,in_shelter,in_cascade,in_mens,in_vets,in_clinical,in_connections,added_at,md5_sum) VALUES ('Joe was hit by a flying banana','accident','2006-01-06 13:30:00','N','N','N','N','Y','N','N','2','2','f','t','f','f','f','f','2006-12-06 13:02:51','ee1dfe13d1dca49e5961bab7158bff1f')
> The Postgres SQL server reported an error.
> The error text was: ERROR: syntax error at or near "(" at character 15
>   
Did you update the engine array after making changes?

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Ok, I managed to update those two files for logs, but I think something =
was gummed up in the process, or came wonky. The fields show up fine in =
the log query screen, but when I attempt to add a log, I get the =
following error, which I regrettably cannot figure out:


Posting log... please stand by
Couldn't query with: INSERT INTO =
(log_text,subject,occurred_at,was_assault_staff,was_threat_staff,was_assa=
ult_client,was_spd,was_medics,was_bar,was_drugs,added_by,changed_by,in_sh=
elter,in_cascade,in_mens,in_vets,in_clinical,in_connections,added_at,md5_=
sum) VALUES ('Joe was hit by a flying banana','accident','2006-01-06 =
13:30:00','N','N','N','N','Y','N','N','2','2','f','t','f','f','f','f','20=
06-12-06 13:02:51','ee1dfe13d1dca49e5961bab7158bff1f')
The Postgres SQL server reported an error.
The error text was: ERROR: syntax error at or near "(" at character 15
The program is continuing
Failed inserting log into table. Record was log_text: Joe was hit by a =
flying banana
subject: accident
occurred_at: 2006-01-06 13:30:00
was_assault_staff: N
was_threat_staff: N
was_assault_client: N
was_spd: N
was_medics: Y
was_bar: N
was_drugs: N
added_by: 2
changed_by: 2
in_shelter: f
in_cascade: t
in_mens: f
in_vets: f
in_clinical: f
in_connections: f
added_at: 2006-12-06 13:02:51
md5_sum: ee1dfe13d1dca49e5961bab7158bff1f

Test DB - not writing to /var/log/chasers/chasers_error.log

Your log entry was not posted.

Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Wed 12/6/2006 10:17 AM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Done! But I'm wondering; will the code 'release' the unit if the =
client's marked as moved out of it? If not, perhaps its best to comment =
it out until that aspect of things can be changed.
>
>  =20
This trigger essentially looks at the unit for the new record, and
checks if anybody is already living in that unit, if so, it rejects the
record, if not, it allows the record to be added. When a person moves
out, an end date is added to the residence record, effectively freeing
the unit for someone else to move into.
> Since you're infinately more familiar with Chasers than I, can you =
think of other aspects of Chasers that will need to be customised for =
CC? I know that some stuff is going to have to be refered to Kiser, but =
off the top of your head, can you think of anything that's pretty DESC =
specific that we can alter before turning to Kiser for input?
>  =20
Did you change the log categories as mentioned in a previous email? This
would be a simple customization. There is also these tables that contain
DESC-specific values:

l_desc_facility
l_desc_program
l_desc_position

You could change values in these in the same way you did l_desc_project.

Other than that, I can't think of anything DESC specific. As you may
already know, we've used CHASERS for rather diverse projects, and very
little customization other than those I've already mentioned was
required. I'll let you know if I think of any more.

Also, I recommend that you start familiarizing yourself with the config
files for the objects you have enabled. These are located in the config
directory, with the naming convention of config_{object}.php. For
residence_desc, this would be config_residence_desc.php.

-Jonathan


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Re: [Chasers-general] Customizing CHASERS

[Ken T. <kt...@de...>]

>
> I'm wondering if shelter, crp, clinical and connections are DESC specif=
ic entries or if they may be included in CompassCenter?
>  =20
A little bit of background might be helpful here. Originally DESC had=20
one log, which was used by the shelter. Eventually, other programs=20
started wanting a log as well. Rather than doing completely separate=20
logs for each program, we built this combined log system. When you write=20
a log, you specify which log (or logs) you want your entry to appear in.=20
When you are reading logs, you can specify which log (or logs) you want=20
to read.

So don't think fields here. Think "which program or programs need a log,=20
and do they need to be separate or not?"

Of course, it may matter what you want to use your logs for. In case=20
it's helpful, here's some background from DESC's log procedure. A short=20
definition:

> A log entry is created to provide other staff with information needed=20
> to get their jobs
> done effectively and safely. Collectively, log entries create a record=20
> of both client
> information and of program operation.
And a little more detail:
> _What information should be logged_
> Logs may contain various types of information, but any occurrence=20
> involving program
> operations or clients that others need to be aware of in order to=20
> conduct their jobs should
> be recorded in a log entry. The most common log entries will contain=20
> information about
> client(s) (including first entries on new clients, and ongoing=20
> information about current
> clients), accounts of unusual or extraordinary incidents (including=20
> bars, calls to SPD or
> medics), and information regarding agency operations. Essentially,=20
> information about
> clients in a log should contribute in some way to better understanding=20
> the client=92s
> circumstances and condition, their unique needs, and any threat to the=20
> safety of other
> clients and staff at DESC.

Figuring out which logs you need is the harder part--adjusting the=20
fields will be relatively easy.

Hope this helps.

Ken

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Ok, in dealing with customizing the logs, I have noticed a few extra entries I haven't seen before:
>
>         in_shelter                      BOOLEAN NOT NULL DEFAULT false,
>         in_morr                 BOOLEAN NOT NULL DEFAULT false,
>         in_union                        BOOLEAN NOT NULL DEFAULT false,
>         in_lyon                 BOOLEAN NOT NULL DEFAULT false,
>         in_ksh                  BOOLEAN NOT NULL DEFAULT false,
>         in_crp                  BOOLEAN NOT NULL DEFAULT false,
>         in_clinical                     BOOLEAN NOT NULL DEFAULT false,
>         in_1811                 BOOLEAN NOT NULL DEFAULT false,
>         in_connections          BOOLEAN NOT NULL DEFAULT false,
>
> I'm wondering if shelter, crp, clinical and connections are DESC specific entries or if they may be included in CompassCenter?
>
>
>   
These are DESC-specific only in that DESC uses all of them. in_1811 will
probably never be applicable to CC, but in_shelter might, if you want to
group all shelter logs into one category, on the other hand, you might
want in_shelter_A and in_shelter_B if you have two shelters, A and B,
that don't really interact. You can really do whatever you want with
these categories. I would play around with the log-entry screen to see
the effects of having different log categories before you move too far
along on deciding what categories make sense for CC.
> Also, with regards to l_desc_position (whole pile of staff titles) and program (admin, clinical, housing), I'm wondering what values there are DESC specific? They do not seem to refer to things I can immediately identify as 'non-Compasscenter'. l_desc_facility was edited previously.
>
>   
There aren't necessarily any DESC-specific values in l_desc_position,
but I mentioned it because you might want to remove ones that will never
be applicable to CC, or add positions that aren't already in there.
Ditto with l_desc_program.

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Ok, in dealing with customizing the logs, I have noticed a few extra =
entries I haven't seen before:

        in_shelter                      BOOLEAN NOT NULL DEFAULT false,
        in_morr                 BOOLEAN NOT NULL DEFAULT false,
        in_union                        BOOLEAN NOT NULL DEFAULT false,
        in_lyon                 BOOLEAN NOT NULL DEFAULT false,
        in_ksh                  BOOLEAN NOT NULL DEFAULT false,
        in_crp                  BOOLEAN NOT NULL DEFAULT false,
        in_clinical                     BOOLEAN NOT NULL DEFAULT false,
        in_1811                 BOOLEAN NOT NULL DEFAULT false,
        in_connections          BOOLEAN NOT NULL DEFAULT false,

I'm wondering if shelter, crp, clinical and connections are DESC =
specific entries or if they may be included in CompassCenter?



Also, with regards to l_desc_position (whole pile of staff titles) and =
program (admin, clinical, housing), I'm wondering what values there are =
DESC specific? They do not seem to refer to things I can immediately =
identify as 'non-Compasscenter'. l_desc_facility was edited previously.


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Fri 12/1/2006 3:17 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Ok, I'm trying to think of a methodical way of going about doing this. =
The first step seems to be to edit the lookup tables and the config =
files in the config directory.
> =20
> Now, since the current database is not influenced by any changes made =
on the current tables or lookup tables within the /database/client =
folder, I can change those sql files with impunity while at the same =
time browsing the current active Chasers database via the admin page =
tables, scouting for values that are DESC centric that need to be erased =
or switched for CC (compass center) values.=20
> =20
> Does changing the config files affect the live database, or is that =
also immune until I reinstall?
>  =20
Changes to the config files take place after you use the "update engine
array" link.
> =20
> Once I've made what changes I can, I will drop and redo the database =
and then go back to those tables, via the admin link and make sure that =
things look the way they should.
> =20
> Does this sound sound?
>  =20
That would be fine.
> =20
> Also, in relation to chasers_config.php, seeing the changes you =
indicate will require dropping the database, simply updating the array, =
or some other step?
No. Changes to chasers_config.php are immediate--this file is read and
parsed for every CHASERS page load.
>  By changing things, I imagine you mean something like this:
>
> $CG_TEXT=3D//General Text Array - this is a first step, the next step
> would be to move this into the db...
> array(
>       //general display...
>     'ORGANIZATION_SHORT' =3D> 'CC',
>     'ORGANIZATION' =3D> 'The Compass Center',
>       'CHASERS_HOME_TITLE' =3D> 'CHASERS Home Page',
> ... snip...
>       'LINK_ORG_HOME'=3D>'Compass Center Home',
>
> =20
> I noticed a lot of DESC centric values in here, from the link to your =
internal website
Somewhere in the config file, there should be a link to
iww.desc.org--this could be changed to the CC site.
>  to the DESC customized logos,
these live in the images directory, and could be replaced by your own =
logo.
>  to other stuff that furrowed my brow:
> =20
> // $log_types need to match the structure of log table:
> $log_types=3Darray("shelter"=3D>"Shelter",
>        "lyon"=3D>"Lyon",
>        "morr"=3D>"Morrison",
>        "union"=3D>"Union",
>        "ksh"=3D>"Kerner-Scott",
>        "crp"=3D>"CRP",
>        "clinical"=3D>"Clinical",
>        '1811'=3D>'1811',
>        'connections'=3D>'Connections'
>  =20
these are the different logs available. I would comment them out all of
them but 1 or 2 to start, and change the labels:

$log_types=3Darray("shelter"=3D>"Cascade",
       "lyon"=3D>"Vets",
//       "morr"=3D>"Morrison",
//      "union"=3D>"Union",
//       "ksh"=3D>"Kerner-Scott",
//       "crp"=3D>"CRP",
//       "clinical"=3D>"Clinical",
//       '1811'=3D>'1811',
//       'connections'=3D>'Connections'

The problem with this first method is that the names are still stored in
the db as in_lyon and in_shelter. If you want, edit create.tbl_log.sql
and change the names like so:

        in_shelter                      BOOLEAN NOT NULL DEFAULT false,
        in_morr                 BOOLEAN NOT NULL DEFAULT false,
        in_union                        BOOLEAN NOT NULL DEFAULT false,
        in_lyon                 BOOLEAN NOT NULL DEFAULT false,
        in_ksh                  BOOLEAN NOT NULL DEFAULT false,
        in_crp                  BOOLEAN NOT NULL DEFAULT false,
        in_clinical                     BOOLEAN NOT NULL DEFAULT false,
        in_1811                 BOOLEAN NOT NULL DEFAULT false,
        in_connections          BOOLEAN NOT NULL DEFAULT false,

to this:

        in_cascade      BOOLEAN NOT NULL DEFAULT false,
        in_vets      BOOLEAN NOT NULL DEFAULT false,
        ..etc..

then, back to chasers_config.php:

$log_types=3Darray("cascade"=3D>"Cascade Womens",
       "vets"=3D>"Vets");

Note: this second method will only work once the db is re-created. Use
the first method to see immediate changes in your test db.


> =20
> I wonder if there are other things lost in the config files that I =
don't know about, and if I should be worrying about them now, or after =
I've done the stuff with the lookup tables?
> =20
> =20
I'm sure there is some stuff in the config files (and table constraints
too), but thoset will make themselves obvious once lookup values are
changed.

-Jonathan


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Done! But I'm wondering; will the code 'release' the unit if the client's marked as moved out of it? If not, perhaps its best to comment it out until that aspect of things can be changed.
>
>   
This trigger essentially looks at the unit for the new record, and
checks if anybody is already living in that unit, if so, it rejects the
record, if not, it allows the record to be added. When a person moves
out, an end date is added to the residence record, effectively freeing
the unit for someone else to move into.
> Since you're infinately more familiar with Chasers than I, can you think of other aspects of Chasers that will need to be customised for CC? I know that some stuff is going to have to be refered to Kiser, but off the top of your head, can you think of anything that's pretty DESC specific that we can alter before turning to Kiser for input?
>   
Did you change the log categories as mentioned in a previous email? This
would be a simple customization. There is also these tables that contain
DESC-specific values:

l_desc_facility
l_desc_program
l_desc_position

You could change values in these in the same way you did l_desc_project.

Other than that, I can't think of anything DESC specific. As you may
already know, we've used CHASERS for rather diverse projects, and very
little customization other than those I've already mentioned was
required. I'll let you know if I think of any more.

Also, I recommend that you start familiarizing yourself with the config
files for the objects you have enabled. These are located in the config
directory, with the naming convention of config_{object}.php. For
residence_desc, this would be config_residence_desc.php.

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Ken T. <kt...@de...>]

>
> can you think of other aspects of Chasers that will need to be customised for CC?
This sounds like where some testing will come in handy.  Everything in 
there more or less "works for us."  I think you folks have to decide if 
it "works for you" too, and if not, what kind of change(s) would be 
needed or desired.

Ken

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Done! But I'm wondering; will the code 'release' the unit if the =
client's marked as moved out of it? If not, perhaps its best to comment =
it out until that aspect of things can be changed.

Since you're infinately more familiar with Chasers than I, can you think =
of other aspects of Chasers that will need to be customised for CC? I =
know that some stuff is going to have to be refered to Kiser, but off =
the top of your head, can you think of anything that's pretty DESC =
specific that we can alter before turning to Kiser for input?


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Wed 12/6/2006 9:30 AM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> That worked very nicely. Just a quick question about functionality; if =
say, we have housing units c1 through c20 for Cascade, does the code =
know not to assign the same unit to different people? Its not terribly =
important, but I was curious, since I suspect that from a user's =
standpoint, this might come up.
>  =20
There are database checks available, but not on by default, for
tbl_residence_desc to not allow people to overlap in the same unit.

To add these checks, I would add these lines to the end of
install.housing.sql:

\i functions/create.functions_residence_desc.sql
CREATE TRIGGER check_residence_desc_record  BEFORE INSERT
    ON tbl_residence_desc FOR EACH ROW
    EXECUTE PROCEDURE residence_desc_verify();

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Ken T. <kt...@de...>]

>
> if say, we have housing units c1 through c20 for Cascade, does the code know not to assign the same unit to different people? 
Database checks are all well and good, but this is primarily a human 
issue.  CHASERS won't be assigning people to units at all.  That is done 
by staff saying "this person lives in this unit."  The units shouldn't 
be arbitrary--each one corresponds to an actual apartment--so it's 
primarily up to staff to enter these correctly.

Ken

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> That worked very nicely. Just a quick question about functionality; if say, we have housing units c1 through c20 for Cascade, does the code know not to assign the same unit to different people? Its not terribly important, but I was curious, since I suspect that from a user's standpoint, this might come up.
>   
There are database checks available, but not on by default, for
tbl_residence_desc to not allow people to overlap in the same unit.

To add these checks, I would add these lines to the end of
install.housing.sql:

\i functions/create.functions_residence_desc.sql
CREATE TRIGGER check_residence_desc_record  BEFORE INSERT
    ON tbl_residence_desc FOR EACH ROW
    EXECUTE PROCEDURE residence_desc_verify();

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

That worked very nicely. Just a quick question about functionality; if =
say, we have housing units c1 through c20 for Cascade, does the code =
know not to assign the same unit to different people? Its not terribly =
important, but I was curious, since I suspect that from a user's =
standpoint, this might come up.


Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Tue 12/5/2006 4:38 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20


Nicholas Burmeister wrote:
> Sorry, I'm afraid I've lost you. I do not remember which previously =
mentioned housing link you refer to. I do vaguely remember back when we =
were pulling our hair out over this one link you sent me that =
essentially forced input into a field that was previously blank. It sort =
of needed a perliminary jumpstart before we could add data. Is that what =
you mean? If so, do you mind recreating it for me? I could spend an hour =
looking for that link in all our emails.
>  =20

At the top of every CHASERS page there should be a link labeled
"housing" in a green box.

>From this page, click the "Add Housing Unit" link (you might first need
to click "Show Empty Records")

> As for creating a batch job, do you want to make me a script that'll =
create 20 for cascade, 100 for mens and 20 for Vets?
>  =20
Eventually you'll need to do this, but for now I would just add a few
units via the user-interface to see what they'll look like.

-Jonathan

-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Sorry, I'm afraid I've lost you. I do not remember which previously mentioned housing link you refer to. I do vaguely remember back when we were pulling our hair out over this one link you sent me that essentially forced input into a field that was previously blank. It sort of needed a perliminary jumpstart before we could add data. Is that what you mean? If so, do you mind recreating it for me? I could spend an hour looking for that link in all our emails.
>   

At the top of every CHASERS page there should be a link labeled
"housing" in a green box.

>From this page, click the "Add Housing Unit" link (you might first need
to click "Show Empty Records")

> As for creating a batch job, do you want to make me a script that'll create 20 for cascade, 100 for mens and 20 for Vets?
>   
Eventually you'll need to do this, but for now I would just add a few
units via the user-interface to see what they'll look like.

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Sorry, I'm afraid I've lost you. I do not remember which previously =
mentioned housing link you refer to. I do vaguely remember back when we =
were pulling our hair out over this one link you sent me that =
essentially forced input into a field that was previously blank. It sort =
of needed a perliminary jumpstart before we could add data. Is that what =
you mean? If so, do you mind recreating it for me? I could spend an hour =
looking for that link in all our emails.

As for creating a batch job, do you want to make me a script that'll =
create 20 for cascade, 100 for mens and 20 for Vets?

Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Tue 12/5/2006 4:17 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Ok, I droped and recrated the db, but the same thing's happening. The =
Unit field has a blank drop down, without any pre-set values, such as =
CAS/MEN/VET or whatever its meant to be. Are there any complete table =
texts I can send you that may show something amiss?
>  =20
You'll still need to create units. This can be done from the
aforementioned housing link using the form. I would start there. If you
have a list of units for each project, those can be batch-imported using
a bit of sql.

-Jonathan

-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Chasers-general mailing list
Cha...@li...
https://lists.sourceforge.net/lists/listinfo/chasers-general

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Ok, I droped and recrated the db, but the same thing's happening. The Unit field has a blank drop down, without any pre-set values, such as CAS/MEN/VET or whatever its meant to be. Are there any complete table texts I can send you that may show something amiss?
>   
You'll still need to create units. This can be done from the
aforementioned housing link using the form. I would start there. If you
have a list of units for each project, those can be batch-imported using
a bit of sql.

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Nicholas B. <nbu...@co...>]

Ok, I droped and recrated the db, but the same thing's happening. The =
Unit field has a blank drop down, without any pre-set values, such as =
CAS/MEN/VET or whatever its meant to be. Are there any complete table =
texts I can send you that may show something amiss?

Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...



-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Tue 12/5/2006 4:02 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> I've gone ahead and edited the table. Here's what the portion in =
question looks like. For now, Aside from the generic "Scattered" and =
"Leased", which I'm leaving in, I'm removing the DESC stuff and putting =
in CAS, MEN and VET, which stand for Cascade, Men's Program and =
Shoreline Vets. There was a special constraint on 1811:
>
>                         WHEN desc_project_housing_code=3D'1811' THEN
> 'E'=3DSUBSTRING(housing_unit_code,1,1)
>                 END)
>
> which I just outright deleted. I hope that's ok. Below is the full =
edit. Let me know if it looks right:
>
> 	CONSTRAINT scattered_address CHECK ((desc_project_housing_code NOT IN =
('SCATTERED','LEASED') AND
> 								(address_1 IS NULL
> 								AND address_2 IS NULL
> 								AND city IS NULL
> 								AND state IS NULL
> 								AND zipcode IS NULL
> 								AND landlord_contact IS NULL))
> 							OR
> 							(desc_project_housing_code =3D 'SCATTERED' AND
> 								(address_1 IS NOT NULL=20
> 								AND city IS NOT NULL
> 								AND state IS NOT NULL
> 								AND zipcode IS NOT NULL
> 								AND landlord_contact IS NOT NULL))
>
> 							OR
> 							(desc_project_housing_code =3D 'LEASED' AND
> 								(address_1 IS NOT NULL=20
> 								AND city IS NOT NULL
> 								AND state IS NOT NULL
> 								AND zipcode IS NOT NULL
> 								AND landlord_contact IS NULL)))
> 	CONSTRAINT only_given_projects CHECK (desc_project_housing_code IN =
('CAS','MEN','VET','SCATTERED','LEASED'))
> 	CONSTRAINT unit_match_project CHECK (
> 			CASE WHEN desc_project_housing_code IN =
('CAS','MEN','VET','SCATTERED')
> 				THEN =
SUBSTRING(desc_project_housing_code,1,1)=3DSUBSTRING(housing_unit_code,1,=
1)
> 			WHEN desc_project_housing_code=3D'LEASED' THEN =
'Z'=3DSUBSTRING(housing_unit_code,1,1)
> 		END)
>
>  =20
This looks fine. Basically the unit_match_project is making sure that,
for example, a unit in "CAS" would be of the form Cxxx, and a unit in
"VET" would be of the form Vxxx where xxx is the unit number...

-Jonathan

Re: [Chasers-general] Customizing CHASERS

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> I've gone ahead and edited the table. Here's what the portion in question looks like. For now, Aside from the generic "Scattered" and "Leased", which I'm leaving in, I'm removing the DESC stuff and putting in CAS, MEN and VET, which stand for Cascade, Men's Program and Shoreline Vets. There was a special constraint on 1811:
>
>                         WHEN desc_project_housing_code='1811' THEN
> 'E'=SUBSTRING(housing_unit_code,1,1)
>                 END)
>
> which I just outright deleted. I hope that's ok. Below is the full edit. Let me know if it looks right:
>
> 	CONSTRAINT scattered_address CHECK ((desc_project_housing_code NOT IN ('SCATTERED','LEASED') AND
> 								(address_1 IS NULL
> 								AND address_2 IS NULL
> 								AND city IS NULL
> 								AND state IS NULL
> 								AND zipcode IS NULL
> 								AND landlord_contact IS NULL))
> 							OR
> 							(desc_project_housing_code = 'SCATTERED' AND
> 								(address_1 IS NOT NULL 
> 								AND city IS NOT NULL
> 								AND state IS NOT NULL
> 								AND zipcode IS NOT NULL
> 								AND landlord_contact IS NOT NULL))
>
> 							OR
> 							(desc_project_housing_code = 'LEASED' AND
> 								(address_1 IS NOT NULL 
> 								AND city IS NOT NULL
> 								AND state IS NOT NULL
> 								AND zipcode IS NOT NULL
> 								AND landlord_contact IS NULL)))
> 	CONSTRAINT only_given_projects CHECK (desc_project_housing_code IN ('CAS','MEN','VET','SCATTERED','LEASED'))
> 	CONSTRAINT unit_match_project CHECK (
> 			CASE WHEN desc_project_housing_code IN ('CAS','MEN','VET','SCATTERED')
> 				THEN SUBSTRING(desc_project_housing_code,1,1)=SUBSTRING(housing_unit_code,1,1)
> 			WHEN desc_project_housing_code='LEASED' THEN 'Z'=SUBSTRING(housing_unit_code,1,1)
> 		END)
>
>   
This looks fine. Basically the unit_match_project is making sure that,
for example, a unit in "CAS" would be of the form Cxxx, and a unit in
"VET" would be of the form Vxxx where xxx is the unit number...

-Jonathan