Menu
▾
▴
chasers-general — General CHASERS list traffic
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(4) |
Jun
(8) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(55) |
Aug
(73) |
Sep
(25) |
Oct
(98) |
Nov
(73) |
Dec
(48) |
| 2007 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Nicholas B. <nbu...@co...> - 2006-12-05 23:54:38
|
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)
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 3:34 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Ok, I got that to work, and then I had to reshuffle some others within =
housing.sql to get the order right, but in the end, it worked out. So =
yay!
>
> Now, however, when I go ahead and get into Chasers, under Adding =
Compass Center Residence, the necessary 'Unit' field is blank (as in, no =
drop down menu provided after my edits to various tables). Can you give =
me a hint where I can edit these values?
>
> =20
Units are added in housing_unit (tbl_housing_unit), from the housing
link we previously had so much difficulty with.
You'll need to alter this table because it has two constraints that
refer to DESC-specific lookup values in l_desc_project:
CONSTRAINT only_given_projects CHECK (desc_project_housing_code
IN ('KSH','LYON','MORR','SCATTERED','UNION','LEASED','1811'))
CONSTRAINT unit_match_project CHECK (
CASE WHEN desc_project_housing_code IN
('KSH','LYON','MORR','SCATTERED','UNION')
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)
WHEN desc_project_housing_code=3D'1811' THEN
'E'=3DSUBSTRING(housing_unit_code,1,1)
END)
You can remove the constraints completely in your test db:
ALTER TABLE tbl_housing_unit DROP CONSTRAINT constraint_name;
and then either comment them out in create.tbl_housing_unit.sql, or edit
them to match whatever codes/naming conventions you come up with for CC
(I would recommend the latter).
-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
|
|
From: Jonathan H. <jhe...@de...> - 2006-12-05 23:35:06
|
Nicholas Burmeister wrote:
> Ok, I got that to work, and then I had to reshuffle some others within housing.sql to get the order right, but in the end, it worked out. So yay!
>
> Now, however, when I go ahead and get into Chasers, under Adding Compass Center Residence, the necessary 'Unit' field is blank (as in, no drop down menu provided after my edits to various tables). Can you give me a hint where I can edit these values?
>
>
Units are added in housing_unit (tbl_housing_unit), from the housing
link we previously had so much difficulty with.
You'll need to alter this table because it has two constraints that
refer to DESC-specific lookup values in l_desc_project:
CONSTRAINT only_given_projects CHECK (desc_project_housing_code
IN ('KSH','LYON','MORR','SCATTERED','UNION','LEASED','1811'))
CONSTRAINT unit_match_project CHECK (
CASE WHEN desc_project_housing_code IN
('KSH','LYON','MORR','SCATTERED','UNION')
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)
WHEN desc_project_housing_code='1811' THEN
'E'=SUBSTRING(housing_unit_code,1,1)
END)
You can remove the constraints completely in your test db:
ALTER TABLE tbl_housing_unit DROP CONSTRAINT constraint_name;
and then either comment them out in create.tbl_housing_unit.sql, or edit
them to match whatever codes/naming conventions you come up with for CC
(I would recommend the latter).
-Jonathan
|
|
From: Nicholas B. <nbu...@co...> - 2006-12-05 21:53:06
|
Ok, I got that to work, and then I had to reshuffle some others within = housing.sql to get the order right, but in the end, it worked out. So = yay! Now, however, when I go ahead and get into Chasers, under Adding Compass = Center Residence, the necessary 'Unit' field is blank (as in, no drop = down menu provided after my edits to various tables). Can you give me a = hint where I can edit these values? 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 11:36 AM To: general Subject: Re: [Chasers-general] Customizing CHASERS =20 Nicholas Burmeister wrote: > Actually, housing is above the cd stuff: > > /* HOUSING-SPECIFIC TABLES */ > \i install.housing.sql > /* Added by Nick - cd */ > \i create.l_service.sql > \i create.l_service_project.sql > =20 move the line above from here > \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 > > The entry in housing.sql looks like this: > > /* housing services*/ > \i create.l_contact_type.sql > \i create.l_service.sql > =20 to here > \i create.tbl_service.sql > \i housing/create.view.l_service_housing.sql > \i create.l_service_project.sql > \i create.view.service_housing.sql > > Halp, I'm going cross-eyed. There's a dependency I am missing. Putting = housing -after- the cd doesn't work eiter, of course. Basically, this error: psql:create.tbl_service.sql:41: ERROR: relation "l_service_project" = does not exist can be interpreted as: tbl_service can't be created because = l_service_project doesn't exist, the fix being to make certain that = l_service_project is created before the script attempts to create = tbl_service. -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 |
|
From: Jonathan H. <jhe...@de...> - 2006-12-05 19:36:22
|
Nicholas Burmeister wrote: > Actually, housing is above the cd stuff: > > /* HOUSING-SPECIFIC TABLES */ > \i install.housing.sql > /* Added by Nick - cd */ > \i create.l_service.sql > \i create.l_service_project.sql > move the line above from here > \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 > > The entry in housing.sql looks like this: > > /* housing services*/ > \i create.l_contact_type.sql > \i create.l_service.sql > to here > \i create.tbl_service.sql > \i housing/create.view.l_service_housing.sql > \i create.l_service_project.sql > \i create.view.service_housing.sql > > Halp, I'm going cross-eyed. There's a dependency I am missing. Putting housing -after- the cd doesn't work eiter, of course. Basically, this error: psql:create.tbl_service.sql:41: ERROR: relation "l_service_project" does not exist can be interpreted as: tbl_service can't be created because l_service_project doesn't exist, the fix being to make certain that l_service_project is created before the script attempts to create tbl_service. -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-05 19:29:22
|
Actually, housing is above the cd stuff: /* HOUSING-SPECIFIC TABLES */ \i install.housing.sql /* Added by Nick - cd */ \i create.l_service.sql \i create.l_service_project.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 The entry in housing.sql looks like this: /* housing services*/ \i create.l_contact_type.sql \i create.l_service.sql \i create.tbl_service.sql \i housing/create.view.l_service_housing.sql \i create.l_service_project.sql \i create.view.service_housing.sql Halp, I'm going cross-eyed. There's a dependency I am missing. Putting = housing -after- the cd doesn't work eiter, of course. 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 11:01 AM To: general Subject: Re: [Chasers-general] Customizing CHASERS =20 Nicholas Burmeister wrote: > Ok, scratch that. I dropped the database and re-ran /i install.sql and = it didn't have that problem. However, when I run it now I'm having = another difficulty. > > psql:create.tbl_service.sql:41: NOTICE: CREATE TABLE will create = implicit sequence "tbl_service_service_id_seq" for serial column = "tbl_service.service_id" > psql:create.tbl_service.sql:41: NOTICE: CREATE TABLE / PRIMARY KEY = will create implicit index "tbl_service_pkey" for table "tbl_service" > psql:create.tbl_service.sql:41: ERROR: relation "l_service_project" = does not exist > psql:create.tbl_service.sql:45: ERROR: current transaction is = aborted, commands ignored until end of transaction block > > I do have a table called l_serivce_project, and install.sql does refer = to it: > > /* Added by Nick - cd */ > \i create.l_service.sql > \i create.l_service_project.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've double checked and create.l_service_project.sql does exist, and = its not misplaced; its in the /database/pg/client folder. > > Here's something I don't understand, tho, of how this install works: = The install.sql script does NOT refer to create.tbl_service.sql. If I = add an install order /i create.tbl_service.sql into the install.sql = script, that doesn't affect things; same error. > > Help me help me! > > > =20 If I remember correctly, you called create.tbl_service.sql in install.housing.sql--You should either move the call to that above the CD stuff, or move the CD stuff below the call to install.housing.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 |
|
From: Jonathan H. <jhe...@de...> - 2006-12-05 19:01:35
|
Nicholas Burmeister wrote: > Ok, scratch that. I dropped the database and re-ran /i install.sql and it didn't have that problem. However, when I run it now I'm having another difficulty. > > psql:create.tbl_service.sql:41: NOTICE: CREATE TABLE will create implicit sequence "tbl_service_service_id_seq" for serial column "tbl_service.service_id" > psql:create.tbl_service.sql:41: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "tbl_service_pkey" for table "tbl_service" > psql:create.tbl_service.sql:41: ERROR: relation "l_service_project" does not exist > psql:create.tbl_service.sql:45: ERROR: current transaction is aborted, commands ignored until end of transaction block > > I do have a table called l_serivce_project, and install.sql does refer to it: > > /* Added by Nick - cd */ > \i create.l_service.sql > \i create.l_service_project.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've double checked and create.l_service_project.sql does exist, and its not misplaced; its in the /database/pg/client folder. > > Here's something I don't understand, tho, of how this install works: The install.sql script does NOT refer to create.tbl_service.sql. If I add an install order /i create.tbl_service.sql into the install.sql script, that doesn't affect things; same error. > > Help me help me! > > > If I remember correctly, you called create.tbl_service.sql in install.housing.sql--You should either move the call to that above the CD stuff, or move the CD stuff below the call to install.housing.sql. -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-05 18:44:55
|
Ok, scratch that. I dropped the database and re-ran /i install.sql and = it didn't have that problem. However, when I run it now I'm having = another difficulty. psql:create.tbl_service.sql:41: NOTICE: CREATE TABLE will create = implicit sequence "tbl_service_service_id_seq" for serial column = "tbl_service.service_id" psql:create.tbl_service.sql:41: NOTICE: CREATE TABLE / PRIMARY KEY will = create implicit index "tbl_service_pkey" for table "tbl_service" psql:create.tbl_service.sql:41: ERROR: relation "l_service_project" = does not exist psql:create.tbl_service.sql:45: ERROR: current transaction is aborted, = commands ignored until end of transaction block I do have a table called l_serivce_project, and install.sql does refer = to it: /* Added by Nick - cd */ \i create.l_service.sql \i create.l_service_project.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've double checked and create.l_service_project.sql does exist, and its = not misplaced; its in the /database/pg/client folder. Here's something I don't understand, tho, of how this install works: The = install.sql script does NOT refer to create.tbl_service.sql. If I add an = install order /i create.tbl_service.sql into the install.sql script, = that doesn't affect things; same error. Help me help me! Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... -----Original Message----- From: cha...@li... on behalf of = Nicholas Burmeister Sent: Mon 12/4/2006 4:23 PM To: general Subject: RE: [Chasers-general] Customizing CHASERS =20 Ok, that was the problem. However, now when I do run /i install.sql, it = starts off just fine, but runs into trouble here: psql:create.tbl_employment_status.sql:35: ERROR: relation = "l_employment_application_status" does not exist psql:create.tbl_employment_status.sql:38: ERROR: current transaction is = aborted, commands ignored until end of transaction block after that its all errors of course. This is sort of an odd error, since = that table certainly does exist. I checked a bit further up the script = run and I noticed some permission denieds: CREATE TABLE CREATE VIEW psql:install.sql:176: create.l_employment_application_status.sql: = Permission denied psql:create.l_employment_level.sql:4: NOTICE: CREATE TABLE / PRIMARY = KEY will create implicit index "l_employment_level_pkey" for table = "l_employment_level"psql:create.l_employment_level.sql:4: NOTICE: = CREATE TABLE / UNIQUE will create implicit index = "l_employment_level_description_key" for table "l_employment_level" CREATE TABLE INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 psql:install.sql:178: create.l_employment_termination.sql: Permission = denied psql:create.l_employment_status.sql:4: NOTICE: CREATE TABLE / PRIMARY = KEY will create implicit index "l_employment_status_pkey" for table = "l_employment_status" psql:create.l_employment_status.sql:4: NOTICE: CREATE TABLE / UNIQUE = will create implicit index "l_employment_status_description_key" for = table "l_employment_status" CREATE TABLE INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 psql:create.tbl_employment_status.sql:35: NOTICE: CREATE TABLE will = create implicit sequence = "tbl_employment_status_employment_status_id_seq" for serial column = "tbl_employment_status.employment_status_id" psql:create.tbl_employment_status.sql:35: NOTICE: CREATE TABLE / = PRIMARY KEY will create implicit index "tbl_employment_status_pkey" for = table "tbl_employment_status" psql:create.tbl_employment_status.sql:35: ERROR: relation = "l_employment_application_status" does not exist All this is a bit odd, because up to that point, it was working just = fine with no errors or permission issues. Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... -----Original Message----- From: cha...@li... on behalf of = Jonathan Hedstrom Sent: Mon 12/4/2006 4:15 PM To: general Subject: Re: [Chasers-general] Customizing CHASERS =20 Nicholas Burmeister wrote: > Oh, I'm sorry I wasn't clear. I did run it the first time, as is = instructed in the wiki as su. I ran this step: > > [root@pchqweb client]# su postgres > bash-3.1$ psql template1 > Welcome to psql 8.1.4, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > template1=3D# \i install.db.sql > psql:install.db.sql:32: ERROR: role "compasscenter" already exists > CREATE DATABASE > You are now connected to database "CompassCenterTest". > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:45: NOTICE: using pg_pltemplate information = instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:60: NOTICE: using pg_pltemplate information = instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > CREATE FUNCTION > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:72: NOTICE: using pg_pltemplate information = instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > SET > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CompassCenterTest=3D# > CompassCenterTest=3D# \q > bash-3.1$ exit > exit > > That worked fine. Its after that, in step 4, that things go pear = shaped. I tried to run it again as su, but simply got this: > =20 You don't need to run it again. After running install.db.sql as postgres, you run install.sql as your new user. I think the confusion is coming from the fact that install.sql used to be called install.db and this change wasn't noted in the install documentation. That as been fixed now though: http://www.desc.org/chasers_wiki/index.php/Installation#CHASERS_DB_instal= l -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-05 00:23:54
|
Ok, that was the problem. However, now when I do run /i install.sql, it = starts off just fine, but runs into trouble here: psql:create.tbl_employment_status.sql:35: ERROR: relation = "l_employment_application_status" does not exist psql:create.tbl_employment_status.sql:38: ERROR: current transaction is = aborted, commands ignored until end of transaction block after that its all errors of course. This is sort of an odd error, since = that table certainly does exist. I checked a bit further up the script = run and I noticed some permission denieds: CREATE TABLE CREATE VIEW psql:install.sql:176: create.l_employment_application_status.sql: = Permission denied psql:create.l_employment_level.sql:4: NOTICE: CREATE TABLE / PRIMARY = KEY will create implicit index "l_employment_level_pkey" for table = "l_employment_level"psql:create.l_employment_level.sql:4: NOTICE: = CREATE TABLE / UNIQUE will create implicit index = "l_employment_level_description_key" for table "l_employment_level" CREATE TABLE INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 psql:install.sql:178: create.l_employment_termination.sql: Permission = denied psql:create.l_employment_status.sql:4: NOTICE: CREATE TABLE / PRIMARY = KEY will create implicit index "l_employment_status_pkey" for table = "l_employment_status" psql:create.l_employment_status.sql:4: NOTICE: CREATE TABLE / UNIQUE = will create implicit index "l_employment_status_description_key" for = table "l_employment_status" CREATE TABLE INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 INSERT 0 1 psql:create.tbl_employment_status.sql:35: NOTICE: CREATE TABLE will = create implicit sequence = "tbl_employment_status_employment_status_id_seq" for serial column = "tbl_employment_status.employment_status_id" psql:create.tbl_employment_status.sql:35: NOTICE: CREATE TABLE / = PRIMARY KEY will create implicit index "tbl_employment_status_pkey" for = table "tbl_employment_status" psql:create.tbl_employment_status.sql:35: ERROR: relation = "l_employment_application_status" does not exist All this is a bit odd, because up to that point, it was working just = fine with no errors or permission issues. Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... -----Original Message----- From: cha...@li... on behalf of = Jonathan Hedstrom Sent: Mon 12/4/2006 4:15 PM To: general Subject: Re: [Chasers-general] Customizing CHASERS =20 Nicholas Burmeister wrote: > Oh, I'm sorry I wasn't clear. I did run it the first time, as is = instructed in the wiki as su. I ran this step: > > [root@pchqweb client]# su postgres > bash-3.1$ psql template1 > Welcome to psql 8.1.4, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > template1=3D# \i install.db.sql > psql:install.db.sql:32: ERROR: role "compasscenter" already exists > CREATE DATABASE > You are now connected to database "CompassCenterTest". > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:45: NOTICE: using pg_pltemplate information = instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:60: NOTICE: using pg_pltemplate information = instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > CREATE FUNCTION > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:72: NOTICE: using pg_pltemplate information = instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > SET > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CompassCenterTest=3D# > CompassCenterTest=3D# \q > bash-3.1$ exit > exit > > That worked fine. Its after that, in step 4, that things go pear = shaped. I tried to run it again as su, but simply got this: > =20 You don't need to run it again. After running install.db.sql as postgres, you run install.sql as your new user. I think the confusion is coming from the fact that install.sql used to be called install.db and this change wasn't noted in the install documentation. That as been fixed now though: http://www.desc.org/chasers_wiki/index.php/Installation#CHASERS_DB_instal= l -Jonathan |
|
From: Jonathan H. <jhe...@de...> - 2006-12-05 00:15:26
|
Nicholas Burmeister wrote: > Oh, I'm sorry I wasn't clear. I did run it the first time, as is instructed in the wiki as su. I ran this step: > > [root@pchqweb client]# su postgres > bash-3.1$ psql template1 > Welcome to psql 8.1.4, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > template1=# \i install.db.sql > psql:install.db.sql:32: ERROR: role "compasscenter" already exists > CREATE DATABASE > You are now connected to database "CompassCenterTest". > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:45: NOTICE: using pg_pltemplate information instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:60: NOTICE: using pg_pltemplate information instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > CREATE FUNCTION > oid > ----- > (0 rows) > > oid > ----- > (0 rows) > > CREATE FUNCTION > psql:install.db.sql:72: NOTICE: using pg_pltemplate information instead of CREA TE LANGUAGE parameters > CREATE LANGUAGE > SET > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CREATE FUNCTION > CompassCenterTest=# > CompassCenterTest=# \q > bash-3.1$ exit > exit > > That worked fine. Its after that, in step 4, that things go pear shaped. I tried to run it again as su, but simply got this: > You don't need to run it again. After running install.db.sql as postgres, you run install.sql as your new user. I think the confusion is coming from the fact that install.sql used to be called install.db and this change wasn't noted in the install documentation. That as been fixed now though: http://www.desc.org/chasers_wiki/index.php/Installation#CHASERS_DB_install -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-04 23:51:17
|
I think I know what the problem is. The wiki should probably say in step = 4 to do /i install.sql, not install.db. Sound right? Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... -----Original Message----- From: cha...@li... on behalf of = Jonathan Hedstrom Sent: Mon 12/4/2006 3:22 PM To: general Subject: Re: [Chasers-general] Customizing CHASERS =20 Nicholas Burmeister wrote: > Ok, I made some changes to two items: > > l_desc_project > l_desc_facility > > Here I added three new items and commented out all DESC housing = entries. I kept the format identical to the ones used by DESC, with the = two last values as true,true > > I then dropped the database via webmin, went into a sql shell via su = postgres and ran the /i install.db.sql. So far so good. However, I think = I have the initial user stuff messed up, since when I then logged into = the databasse as user 'compasscenter' and tried the /i install.db.sql = again, I got permission errors: > > [root@pchqweb client]# psql -U compasscenter CompassCenterTest > Welcome to psql 8.1.4, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > CompassCenterTest=3D> \i install.db > install.db: No such file or directory > CompassCenterTest=3D> \i install.db.sql > psql:install.db.sql:32: ERROR: permission denied to create role > psql:install.db.sql:33: ERROR: permission denied to create database > =20 You need to run install.db.sql as the superuser postgres. -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-04 23:35:35
|
Oh, I'm sorry I wasn't clear. I did run it the first time, as is =
instructed in the wiki as su. I ran this step:
[root@pchqweb client]# su postgres
bash-3.1$ psql template1
Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
template1=3D# \i install.db.sql
psql:install.db.sql:32: ERROR: role "compasscenter" already exists
CREATE DATABASE
You are now connected to database "CompassCenterTest".
oid
-----
(0 rows)
oid
-----
(0 rows)
CREATE FUNCTION
psql:install.db.sql:45: NOTICE: using pg_pltemplate information instead =
of CREA TE LANGUAGE parameters
CREATE LANGUAGE
oid
-----
(0 rows)
oid
-----
(0 rows)
CREATE FUNCTION
psql:install.db.sql:60: NOTICE: using pg_pltemplate information instead =
of CREA TE LANGUAGE parameters
CREATE LANGUAGE
CREATE FUNCTION
oid
-----
(0 rows)
oid
-----
(0 rows)
CREATE FUNCTION
psql:install.db.sql:72: NOTICE: using pg_pltemplate information instead =
of CREA TE LANGUAGE parameters
CREATE LANGUAGE
SET
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CompassCenterTest=3D#
CompassCenterTest=3D# \q
bash-3.1$ exit
exit
That worked fine. Its after that, in step 4, that things go pear shaped. =
I tried to run it again as su, but simply got this:
[root@pchqweb client]# su postgres
bash-3.1$ psql CompassCenterTest
Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
CompassCenterTest=3D# \i install.db.sql
psql:install.db.sql:32: ERROR: role "compasscenter" already exists
psql:install.db.sql:33: ERROR: database "CompassCenterTest" already =
exists
You are now connected to database "CompassCenterTest".
oid
-------
23268
(1 row)
oid
-------
23266
23265
(2 rows)
psql:install.db.sql:44: ERROR: function "plpgsql_call_handler" already =
exists with same argument types
psql:install.db.sql:45: ERROR: language "plpgsql" already exists
oid
-------
23271
(1 row)
oid
-------
23270
23269
(2 rows)
psql:install.db.sql:59: ERROR: function "pltclu_call_handler" already =
exists with same argument types
psql:install.db.sql:60: ERROR: language "pltclu" already exists
psql:install.db.sql:66: ERROR: function "pgmail" already exists with =
same argument types
oid
-------
23275
(1 row)
oid
-------
23274
23273
(2 rows)
psql:install.db.sql:71: ERROR: function "pltcl_call_handler" already =
exists with same argument types
psql:install.db.sql:72: ERROR: language "pltcl" already exists
SET
psql:install.db.sql:83: ERROR: function "levenshtein" already exists =
with same argument types
psql:install.db.sql:88: ERROR: function "metaphone" already exists with =
same argument types
psql:install.db.sql:92: ERROR: function "soundex" already exists with =
same argument types
psql:install.db.sql:96: ERROR: function "text_soundex" already exists =
with same argument types
psql:install.db.sql:110: ERROR: function "table_log" already exists =
with same argument types
psql:install.db.sql:113: ERROR: function "table_log_restore_table" =
already exists with same argument types
psql:install.db.sql:116: ERROR: function "table_log_restore_table" =
already exists with same argument types
psql:install.db.sql:119: ERROR: function "table_log_restore_table" =
already exists with same argument types
psql:install.db.sql:122: ERROR: function "table_log_restore_table" =
already exists with same argument types
CompassCenterTest=3D#
Updating the engine array gives me this output.
Updating and storing in Engine Array: engine
No config file found for client_ref. Will configure client_ref using =
engine defaults.
Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation =
"help" does not exist in /var/www/html/chasers/sql_layer.php on line 30
SELECT help_text from Help WHERE title=3D'Non-DESC Living Situations'
The Postgres SQL server reported an error.
The error text was: ERROR: relation "help" does not exist
The program is continuing
Warning: pg_fetch_array() expects parameter 1 to be resource, boolean =
given in /var/www/html/chasers/sql_layer.php on line 448
Configuring client
Configuring client_death
Configuring client_note
Configuring client_protected
Configuring client_ref
Configuring contact_information
Configuring disability
Configuring employment_status
Configuring income
Configuring phone
Configuring staff_assign
Configuring charge
Configuring housing_notice
Configuring housing_rsp
Configuring housing_unit
Configuring housing_unit_subsidy
Configuring payment
Configuring residence_desc
Configuring residence_other
Configuring service_housing
Configuring housing_history
Configuring application_housing
Configuring cd_reg
Configuring service_cd
Configuring alert
Configuring alert_notify
Configuring staff
Configuring permission
Configuring staff_employment
Configuring user_option
Configuring generic_sql_query
Configuring pg_catalog
UPDATING CONFIGURATION ARRAY IN DB
Couldn't query with: SELECT *
FROM tbl_engine_config
WHERE val_name =3D 'engine'
The Postgres SQL server reported an error.
The error text was: ERROR: relation "tbl_engine_config" does not exist
The program is continuing
Then followed a BUNCH of output that's too long to post to Sourceforge.
Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...
-----Original Message-----
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Mon 12/4/2006 3:22 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
=20
Nicholas Burmeister wrote:
> Ok, I made some changes to two items:
>
> l_desc_project
> l_desc_facility
>
> Here I added three new items and commented out all DESC housing =
entries. I kept the format identical to the ones used by DESC, with the =
two last values as true,true
>
> I then dropped the database via webmin, went into a sql shell via su =
postgres and ran the /i install.db.sql. So far so good. However, I think =
I have the initial user stuff messed up, since when I then logged into =
the databasse as user 'compasscenter' and tried the /i install.db.sql =
again, I got permission errors:
>
> [root@pchqweb client]# psql -U compasscenter CompassCenterTest
> Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> CompassCenterTest=3D> \i install.db
> install.db: No such file or directory
> CompassCenterTest=3D> \i install.db.sql
> psql:install.db.sql:32: ERROR: permission denied to create role
> psql:install.db.sql:33: ERROR: permission denied to create database
> =20
You need to run install.db.sql as the superuser postgres.
-Jonathan
|
|
From: Jonathan H. <jhe...@de...> - 2006-12-04 23:22:20
|
Nicholas Burmeister wrote: > Ok, I made some changes to two items: > > l_desc_project > l_desc_facility > > Here I added three new items and commented out all DESC housing entries. I kept the format identical to the ones used by DESC, with the two last values as true,true > > I then dropped the database via webmin, went into a sql shell via su postgres and ran the /i install.db.sql. So far so good. However, I think I have the initial user stuff messed up, since when I then logged into the databasse as user 'compasscenter' and tried the /i install.db.sql again, I got permission errors: > > [root@pchqweb client]# psql -U compasscenter CompassCenterTest > Welcome to psql 8.1.4, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > CompassCenterTest=> \i install.db > install.db: No such file or directory > CompassCenterTest=> \i install.db.sql > psql:install.db.sql:32: ERROR: permission denied to create role > psql:install.db.sql:33: ERROR: permission denied to create database > You need to run install.db.sql as the superuser postgres. -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-04 23:17:01
|
Ok, I made some changes to two items:
l_desc_project
l_desc_facility
Here I added three new items and commented out all DESC housing entries. =
I kept the format identical to the ones used by DESC, with the two last =
values as true,true
I then dropped the database via webmin, went into a sql shell via su =
postgres and ran the /i install.db.sql. So far so good. However, I think =
I have the initial user stuff messed up, since when I then logged into =
the databasse as user 'compasscenter' and tried the /i install.db.sql =
again, I got permission errors:
[root@pchqweb client]# psql -U compasscenter CompassCenterTest
Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
CompassCenterTest=3D> \i install.db
install.db: No such file or directory
CompassCenterTest=3D> \i install.db.sql
psql:install.db.sql:32: ERROR: permission denied to create role
psql:install.db.sql:33: ERROR: permission denied to create database
You are now connected to database "CompassCenterTest".
oid
-------
23268
(1 row)
oid
-------
23266
23265
(2 rows)
psql:install.db.sql:44: ERROR: permission denied for language c
psql:install.db.sql:45: ERROR: must be superuser to create procedural =
language
etc etc etc.
I checked the permissions for the user compasscenter, and sure enough, =
it can't create a database. Should I be logging into the sql shell using =
su, or with the newly created user (nburmeister) from =
add_initial_user.sql?=20
I can log into it as compasscenter, but not do any modifications as =
asked to do in step 4 of the wiki instructions. On a side note, is that =
a typo in the wiki? Do you really mean install.db, not install.db.sql?
4. run psql as the newly created user (from step 1 and 2):
# psql -U {USER} {DATABASE}=20
{DATABASE}# \i install.db=20
Regardless, when I tried to log into chasers after the first simple =
install using su postgres, updating the engine array failed =
spectacularly. So where to start!
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
|
|
From: Ken T. <kt...@de...> - 2006-12-01 23:17:59
|
> > Also, I wanted to mention that I am currently in the process of building a new linux server for the excercise of trying to get Chasers up and running again on a second computer. I'm making progress with it, already having installed all the necessary packages, including the pesky zzip tool and libraries and the table logs, but I am running into a few walls here and there. Our initial 'documentation' on the Sourceforge site is often hard to read, out of order due to outages of the Sourceforge site and often refers to steps done out of order to the natural installation of Chasers to be of use. It was, after all, our first try, and there was an awful lot of stumbling about in the dark. I'm relying on them as much as is possible without going insane, but I'm hoping you guys will be open to questions as I go along. Here's a couple of quick thoughts about this: The mailing list stuff is great for at least getting some record of what's been going on, but ultimately it will be better suited to resolving specific issues/troubleshooting than for looking up general, common information like the basic steps for installing CHASERS. For that kind of information, we'd like to get to the point where the wiki is an accurate source of documentation. This is an area where you could be very helpful. We'd already put out a draft of what's needed to install, but clearly missed some stuff. Partly that's because we've used it so much, and therefore might not spell out things that in fact won't be obvious to other people. Also, you've ran into problems because you're starting from scratch, that may never appear to us here. Your experience in installing CHASERS is going to be much closer to what other users will experience. All of this is to say, I'd suggest that we help you with questions as they come up, and you in turn update the installation section of the Wiki so it really is accurate (or a lot closer than it is now). Does that sound like a reasonable plan? Let me know. Thanks. Ken p.s., A quick note regarding the SF mailing list. Part of the reason it's hard to read is that there are some "threading" issues where many emails are all showing up as part of one chain. This is happening even when the subject gets changed. We think this comes from hitting "reply", rather than starting a new message. So if you're starting a new thread, don't just "reply" and change the subject, but start with a fresh, blank email instead. If the new thread refers to stuff in the previous email, just copy/paste it into the new one. Hopefully this will make the archive more useful as we go forward! Nicholas Burmeister wrote: > Ken, Jon, > > I've managed to add an entry for Cascade into the l_desc_project table successfuly. > > I'm wondering if its more productive to simply edit the code, including the actual names of the lookup tables (from l_desc_project to, say l_compass_project), since the desired result is a new, compasscenter-only database. Since the process involved is often simple word substitution, perhaps we should just change the housing names across the board to an equivalent Compass Center name, say, substitute Kerner for Cascade, adding entries if necessary and then simply drop and redo the database. > > Let me know what you think might be the wisest way to proceed. > > Also, I wanted to mention that I am currently in the process of building a new linux server for the excercise of trying to get Chasers up and running again on a second computer. I'm making progress with it, already having installed all the necessary packages, including the pesky zzip tool and libraries and the table logs, but I am running into a few walls here and there. Our initial 'documentation' on the Sourceforge site is often hard to read, out of order due to outages of the Sourceforge site and often refers to steps done out of order to the natural installation of Chasers to be of use. It was, after all, our first try, and there was an awful lot of stumbling about in the dark. I'm relying on them as much as is possible without going insane, but I'm hoping you guys will be open to questions as I go along. > > If so, since this is a 'second' project, can I direct questions to you about it outside the Sourceforge site, or do you prefer that I keep sending all inquiries, however disparate, to chasers-general? > > > Nicholas Burmeister > IT Department > The Compass Center > 206-357-3144 > nbu...@co... > > > ________________________________ > > From: cha...@li... on behalf of Jonathan Hedstrom > Sent: Tue 11/28/2006 10:42 AM > To: general > Subject: [Chasers-general] Customizing CHASERS > > > > Nicholas Burmeister wrote: > >> I do believe we've finished with the tables that we needed. I guess now we need to go ahead and customise things a bit for Compass Center. I noticed in one of our emails that some things can be edited directly from within Chasers administration. So there I went, all eager to edit something! And behold, a spam of errors occured after Client Unduplication and before Update Chasers from Shamis: >> >> Warning: filemtime() [function.filemtime]: stat failed for /shared/is/mh45/ma-dal.db in /var/www/html/chasers/chasers_admin.php on line 163 >> >> Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation "clin_dal" does not exist in /var/www/html/chasers/sql_layer.php on line 30 >> >> Warning: pg_fetch_array() expects parameter 1 to be resource, boolean given in /var/www/html/chasers/sql_layer.php on line 448 >> >> Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation "clin_tauth" does not exist in /var/www/html/chasers/sql_layer.php on line 30 >> >> Warning: pg_fetch_array() expects parameter 1 to be resource, boolean given in /var/www/html/chasers/sql_layer.php on line 448 >> >> Are you interested in addressing this now, >> > You should be able to comment these out in chasers_admin.php. > >> or do you want to go ahead and teach me how to remove DESC specific stuff and add the Compass Center stuff that we know will be needed, such as housing sites that are know (Vets, Cascade, etc)? >> >> > The best place to start customizing CHASERS is probably in the lookup > tables, and in the config files located in the config directory. You've > already done a bit with the config files (changing data_type to phone > for the contact_information records, adding child records to > config_client.php etc). > > For example, to change the "DESC residence" to something else, you would > change these two lines in config/config_residence_desc.php: > > 'singular'=>'DESC Residence', > 'plural'=>'DESC Residencies', > > > For more on config file options, take a look at the config file section > of the CHASERS engine documentation: > http://www.desc.org/chasers_wiki/index.php/Engine_Documentation:_Configuration_File_Options_for_Engine > > If you go to the CHASERS Admin page and click the link that reads "List > all DB tables", you'll get a list of all the tables in the database. The > ones that start with "l_" are lookup tables. These tables contain the > values that appear on the various drop lists you are presented with when > you add records to CHASERS. > > For example, if you want to get rid of the Morrison, Kerner-Scott House, > etc, find the link to the table "l_desc_project". This table contains a > list of all the DESC projects. If you delete these records, and then add > Vets and Cascade, you'll be able to add units to housing_unit for these > projects, and then move people into those units. > > Note: since you have most likely already added data to the test database > that references l_desc_project, you probably won't be able to delete all > the DESC-specific records in this table. > > Using the admin page is fine for testing and tweaking an existing > installation, but while you are doing so, keep in mind that the files > that initially populates these lookups are in database/pg/client and can > be changed there if you want the effects to be included when you create > the live database. > > To continue the example from above, create.l_desc_project.sql looks like > this: > > CREATE TABLE l_desc_project ( > desc_project_code VARCHAR(10) PRIMARY KEY, > description VARCHAR(80) NOT NULL UNIQUE, > desc_program_code VARCHAR(10) NOT NULL REFERENCES > l_desc_program (desc_program_code), > auto_calculate_subsidy_charges BOOLEAN, > auto_calculate_rent_charges BOOLEAN > ); > > > > INSERT INTO l_desc_project VALUES ('KSH', 'Kerner-Scott > House','HOUSING', true, true); > INSERT INTO l_desc_project VALUES ('ACCOUNT', 'Accounting','ADMIN', > null, null); > INSERT INTO l_desc_project VALUES ('ALL', '(For the E.D.)','ADMIN', > null, null); > INSERT INTO l_desc_project VALUES ('CD', 'Chemical Dependency > Program','CLINICAL', null, null); > INSERT INTO l_desc_project VALUES ('CLINADMIN', 'Clinical > Administration','CLINICAL', null, null); > INSERT INTO l_desc_project VALUES ('CRP', 'Crisis Respite > Program','CLINICAL', null, null); > INSERT INTO l_desc_project VALUES ('DEVEL', 'Fund Development','ADMIN', > null, null); > INSERT INTO l_desc_project VALUES ('FACIL', 'Facilities','ADMIN', null, > null); > INSERT INTO l_desc_project VALUES ('HCH', 'Health Care for the > Homeless','CLINICAL', null, null); > INSERT INTO l_desc_project VALUES ('HOST', 'HOST Program','CLINICAL', > null, null); > INSERT INTO l_desc_project VALUES ('HOUSADMIN', 'Housing > Administration','ADMIN', null, null); > INSERT INTO l_desc_project VALUES ('HOUSONCALL', 'Housing On-Call > (multiple projects)','HOUSING', null, null); > INSERT INTO l_desc_project VALUES ('IR', 'Information & > Referral','ADMIN', null, null); > INSERT INTO l_desc_project VALUES ('IS', 'Information Services','ADMIN', > null, null); > INSERT INTO l_desc_project VALUES ('HEET', 'HEET Program','HOUSING', > null, null); > INSERT INTO l_desc_project VALUES ('KSSHEL', 'Kerner-Scott Women''s > Shelter','HOUSING', null, null); > INSERT INTO l_desc_project VALUES ('LYON', 'The Lyon > Building','HOUSING', true, true); > INSERT INTO l_desc_project VALUES ('MEDICAL', 'Medical > Staff','CLINICAL', null, null); > INSERT INTO l_desc_project VALUES ('MORR', 'The Morrison','HOUSING', > true, true); > INSERT INTO l_desc_project VALUES ('SAGE', 'SAGE Program','CLINICAL', > null, null); > INSERT INTO l_desc_project VALUES ('SHELTER', 'Shelter > Program','HOUSING', null, null); > INSERT INTO l_desc_project VALUES ('SUPPORT', 'Administrative > Support','ADMIN', null, null); > INSERT INTO l_desc_project VALUES ('UNION', 'The Union Hotel','HOUSING', > true, true); > INSERT INTO l_desc_project VALUES ('SCATTERED', 'Scattered Site > Housing','HOUSING', false, false); > INSERT INTO l_desc_project VALUES ('LEASED', 'Scattered Site > (Leased)','HOUSING', false, true); > > If you comment out all those "INSERT INTO ..." lines, and then add your > own (obviously changing the description), your new database will be > created with only those 2 projects available: > > INSERT INTO l_desc_project VALUES ('VETS', 'A more readable description > goes here','HOUSING', true, true); > INSERT INTO l_desc_project VALUES ('CASCADE', 'A more readable > description goes here','HOUSING', true, true); > > (you'll need to decide about auto-calculating subsidies and rents, but > that's what those last 2 values are all about) > > So to summarize, I would recommend playing around on the Admin page to > see what effect the values in the lookup tables have, and then see what > you can do with the config files. > > -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=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > Chasers-general mailing list > Cha...@li... > https://lists.sourceforge.net/lists/listinfo/chasers-general > |
|
From: Jonathan H. <jhe...@de...> - 2006-12-01 23:17:23
|
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. > > 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. > > Does changing the config files affect the live database, or is that also immune until I reinstall? > Changes to the config files take place after you use the "update engine array" link. > > 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. > > Does this sound sound? > That would be fine. > > 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=//General Text Array - this is a first step, the next step > would be to move this into the db... > array( > //general display... > 'ORGANIZATION_SHORT' => 'CC', > 'ORGANIZATION' => 'The Compass Center', > 'CHASERS_HOME_TITLE' => 'CHASERS Home Page', > ... snip... > 'LINK_ORG_HOME'=>'Compass Center Home', > > > 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: > > // $log_types need to match the structure of log table: > $log_types=array("shelter"=>"Shelter", > "lyon"=>"Lyon", > "morr"=>"Morrison", > "union"=>"Union", > "ksh"=>"Kerner-Scott", > "crp"=>"CRP", > "clinical"=>"Clinical", > '1811'=>'1811', > 'connections'=>'Connections' > 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=array("shelter"=>"Cascade", "lyon"=>"Vets", // "morr"=>"Morrison", // "union"=>"Union", // "ksh"=>"Kerner-Scott", // "crp"=>"CRP", // "clinical"=>"Clinical", // '1811'=>'1811', // 'connections'=>'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=array("cascade"=>"Cascade Womens", "vets"=>"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. > > 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? > > 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 |
|
From: Nicholas B. <nbu...@co...> - 2006-12-01 22:58:08
|
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
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
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? 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 to the DESC customized logos, 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
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
Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...
=20
________________________________
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Fri 12/1/2006 2:17 PM
To: general
Subject: Re: [Chasers-general] Customizing CHASERS
Nicholas Burmeister wrote:
> Ok, so changing the table names, or even the lookup table names, is =
out, and that makes sense to me.
>=20
> With regards to word substitution, I think I know what you mean, but I =
want to be sure I understand you. When I said to substitute Kerner for =
Cascade, I was refering to values within a lookup table, not the name of =
any table itself. This is what you meant, right?
> =20
Yes, I meant lookup table values.
>=20
> As for not changing anything labled DESC, do you mean that with =
reference to table titles, both regular and lookup, or do you mean =
including any values within a table labled DESC?
I just meant to be cautious if you planned on using a blind search and
replace. Changing DESC in a config file or in a lookup table value
shouldn't have any detrimental effects, but if you simply tried to
change all instances of the 4 letters "desc" to something like cascade,
you would change a query like this:
SELECT * FROM l_sample_table ORDER BY sample_table_code DESC;
(which runs)
to something that doesn't make any sense.
On a related note, you might have already come across this, but there is
a variable in chasers_config.php that allows you to quickly change the
organization name:
$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> 'DESC',
'ORGANIZATION' =3D> 'Downtown Emergency Service Center',
'CHASERS_HOME_TITLE' =3D> 'CHASERS Home Page',
... snip...
'LINK_ORG_HOME'=3D>'DESC Home',
=20
-Jonathan
|
|
From: Jonathan H. <jhe...@de...> - 2006-12-01 22:17:15
|
Nicholas Burmeister wrote:
> Ok, so changing the table names, or even the lookup table names, is out, and that makes sense to me.
>
> With regards to word substitution, I think I know what you mean, but I want to be sure I understand you. When I said to substitute Kerner for Cascade, I was refering to values within a lookup table, not the name of any table itself. This is what you meant, right?
>
Yes, I meant lookup table values.
>
> As for not changing anything labled DESC, do you mean that with reference to table titles, both regular and lookup, or do you mean including any values within a table labled DESC?
I just meant to be cautious if you planned on using a blind search and
replace. Changing DESC in a config file or in a lookup table value
shouldn't have any detrimental effects, but if you simply tried to
change all instances of the 4 letters "desc" to something like cascade,
you would change a query like this:
SELECT * FROM l_sample_table ORDER BY sample_table_code DESC;
(which runs)
to something that doesn't make any sense.
On a related note, you might have already come across this, but there is
a variable in chasers_config.php that allows you to quickly change the
organization name:
$CG_TEXT=//General Text Array - this is a first step, the next step
would be to move this into the db...
array(
//general display...
'ORGANIZATION_SHORT' => 'DESC',
'ORGANIZATION' => 'Downtown Emergency Service Center',
'CHASERS_HOME_TITLE' => 'CHASERS Home Page',
... snip...
'LINK_ORG_HOME'=>'DESC Home',
-Jonathan
|
|
From: Nicholas B. <nbu...@co...> - 2006-12-01 22:02:58
|
Ok, so changing the table names, or even the lookup table names, is out, = and that makes sense to me. =20 With regards to word substitution, I think I know what you mean, but I = want to be sure I understand you. When I said to substitute Kerner for = Cascade, I was refering to values within a lookup table, not the name of = any table itself. This is what you meant, right? =20 As for not changing anything labled DESC, do you mean that with = reference to table titles, both regular and lookup, or do you mean = including any values within a table labled DESC? =20 Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... =20 ________________________________ From: cha...@li... on behalf of = Jonathan Hedstrom Sent: Fri 12/1/2006 1:56 PM To: general Subject: Re: [Chasers-general] Customizing CHASERS Nicholas Burmeister wrote: > Ken, Jon, >=20 > I've managed to add an entry for Cascade into the l_desc_project table = successfuly. >=20 > I'm wondering if its more productive to simply edit the code, = including the actual names of the lookup tables (from l_desc_project to, = say l_compass_project), since the desired result is a new, = compasscenter-only database. Changing the names of tables would be a lot of work (the reason being that they could be hard-coded in the code, or in the case of a lookup table, referenced in many other tables). I would strongly recommend against it. Once you have the values stored in the tables correct, the user will almost certainly never see, for example, that the table is called l_desc_project. > Since the process involved is often simple word substitution, perhaps = we should just change the housing names across the board to an = equivalent Compass Center name, say, substitute Kerner for Cascade, = adding entries if necessary and then simply drop and redo the database. > =20 There shouldn't be a table called Kerner, but as far as changing the values stored in the table, this would be a fine way to proceed. (Note: you wouldn't want to do this for DESC, since that is an SQL keyword for sorting queries). -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 |
|
From: Jonathan H. <jhe...@de...> - 2006-12-01 21:56:43
|
Nicholas Burmeister wrote: > Ken, Jon, > > I've managed to add an entry for Cascade into the l_desc_project table successfuly. > > I'm wondering if its more productive to simply edit the code, including the actual names of the lookup tables (from l_desc_project to, say l_compass_project), since the desired result is a new, compasscenter-only database. Changing the names of tables would be a lot of work (the reason being that they could be hard-coded in the code, or in the case of a lookup table, referenced in many other tables). I would strongly recommend against it. Once you have the values stored in the tables correct, the user will almost certainly never see, for example, that the table is called l_desc_project. > Since the process involved is often simple word substitution, perhaps we should just change the housing names across the board to an equivalent Compass Center name, say, substitute Kerner for Cascade, adding entries if necessary and then simply drop and redo the database. > There shouldn't be a table called Kerner, but as far as changing the values stored in the table, this would be a fine way to proceed. (Note: you wouldn't want to do this for DESC, since that is an SQL keyword for sorting queries). -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-12-01 21:45:32
|
Ken, Jon,
=20
I've managed to add an entry for Cascade into the l_desc_project table =
successfuly.
=20
I'm wondering if its more productive to simply edit the code, including =
the actual names of the lookup tables (from l_desc_project to, say =
l_compass_project), since the desired result is a new, =
compasscenter-only database. Since the process involved is often simple =
word substitution, perhaps we should just change the housing names =
across the board to an equivalent Compass Center name, say, substitute =
Kerner for Cascade, adding entries if necessary and then simply drop and =
redo the database.
=20
Let me know what you think might be the wisest way to proceed.
=20
Also, I wanted to mention that I am currently in the process of building =
a new linux server for the excercise of trying to get Chasers up and =
running again on a second computer. I'm making progress with it, already =
having installed all the necessary packages, including the pesky zzip =
tool and libraries and the table logs, but I am running into a few walls =
here and there. Our initial 'documentation' on the Sourceforge site is =
often hard to read, out of order due to outages of the Sourceforge site =
and often refers to steps done out of order to the natural installation =
of Chasers to be of use. It was, after all, our first try, and there was =
an awful lot of stumbling about in the dark. I'm relying on them as much =
as is possible without going insane, but I'm hoping you guys will be =
open to questions as I go along.
=20
If so, since this is a 'second' project, can I direct questions to you =
about it outside the Sourceforge site, or do you prefer that I keep =
sending all inquiries, however disparate, to chasers-general?
=20
=20
Nicholas Burmeister
IT Department
The Compass Center
206-357-3144
nbu...@co...
=20
________________________________
From: cha...@li... on behalf of =
Jonathan Hedstrom
Sent: Tue 11/28/2006 10:42 AM
To: general
Subject: [Chasers-general] Customizing CHASERS
Nicholas Burmeister wrote:
> I do believe we've finished with the tables that we needed. I guess =
now we need to go ahead and customise things a bit for Compass Center. I =
noticed in one of our emails that some things can be edited directly =
from within Chasers administration. So there I went, all eager to edit =
something! And behold, a spam of errors occured after Client =
Unduplication and before Update Chasers from Shamis:
>=20
> Warning: filemtime() [function.filemtime]: stat failed for =
/shared/is/mh45/ma-dal.db in /var/www/html/chasers/chasers_admin.php on =
line 163
>
> Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation =
"clin_dal" does not exist in /var/www/html/chasers/sql_layer.php on line =
30
>
> Warning: pg_fetch_array() expects parameter 1 to be resource, boolean =
given in /var/www/html/chasers/sql_layer.php on line 448
>
> Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation =
"clin_tauth" does not exist in /var/www/html/chasers/sql_layer.php on =
line 30
>
> Warning: pg_fetch_array() expects parameter 1 to be resource, boolean =
given in /var/www/html/chasers/sql_layer.php on line 448
>
> Are you interested in addressing this now,
You should be able to comment these out in chasers_admin.php.
> or do you want to go ahead and teach me how to remove DESC specific =
stuff and add the Compass Center stuff that we know will be needed, such =
as housing sites that are know (Vets, Cascade, etc)?
> =20
The best place to start customizing CHASERS is probably in the lookup
tables, and in the config files located in the config directory. You've
already done a bit with the config files (changing data_type to phone
for the contact_information records, adding child records to
config_client.php etc).
For example, to change the "DESC residence" to something else, you would
change these two lines in config/config_residence_desc.php:
'singular'=3D>'DESC =
Residence',
'plural'=3D>'DESC =
Residencies',
For more on config file options, take a look at the config file section
of the CHASERS engine documentation:
http://www.desc.org/chasers_wiki/index.php/Engine_Documentation:_Configur=
ation_File_Options_for_Engine
If you go to the CHASERS Admin page and click the link that reads "List
all DB tables", you'll get a list of all the tables in the database. The
ones that start with "l_" are lookup tables. These tables contain the
values that appear on the various drop lists you are presented with when
you add records to CHASERS.
For example, if you want to get rid of the Morrison, Kerner-Scott House,
etc, find the link to the table "l_desc_project". This table contains a
list of all the DESC projects. If you delete these records, and then add
Vets and Cascade, you'll be able to add units to housing_unit for these
projects, and then move people into those units.
Note: since you have most likely already added data to the test database
that references l_desc_project, you probably won't be able to delete all
the DESC-specific records in this table.
Using the admin page is fine for testing and tweaking an existing
installation, but while you are doing so, keep in mind that the files
that initially populates these lookups are in database/pg/client and can
be changed there if you want the effects to be included when you create
the live database.
To continue the example from above, create.l_desc_project.sql looks like
this:
CREATE TABLE l_desc_project (
desc_project_code VARCHAR(10) PRIMARY KEY,
description VARCHAR(80) NOT NULL UNIQUE,
desc_program_code VARCHAR(10) NOT NULL REFERENCES
l_desc_program (desc_program_code),
auto_calculate_subsidy_charges BOOLEAN,
auto_calculate_rent_charges BOOLEAN
);
INSERT INTO l_desc_project VALUES ('KSH', 'Kerner-Scott
House','HOUSING', true, true);
INSERT INTO l_desc_project VALUES ('ACCOUNT', 'Accounting','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('ALL', '(For the E.D.)','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('CD', 'Chemical Dependency
Program','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('CLINADMIN', 'Clinical
Administration','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('CRP', 'Crisis Respite
Program','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('DEVEL', 'Fund Development','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('FACIL', 'Facilities','ADMIN', null,
null);
INSERT INTO l_desc_project VALUES ('HCH', 'Health Care for the
Homeless','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('HOST', 'HOST Program','CLINICAL',
null, null);
INSERT INTO l_desc_project VALUES ('HOUSADMIN', 'Housing
Administration','ADMIN', null, null);
INSERT INTO l_desc_project VALUES ('HOUSONCALL', 'Housing On-Call
(multiple projects)','HOUSING', null, null);
INSERT INTO l_desc_project VALUES ('IR', 'Information &
Referral','ADMIN', null, null);
INSERT INTO l_desc_project VALUES ('IS', 'Information Services','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('HEET', 'HEET Program','HOUSING',
null, null);
INSERT INTO l_desc_project VALUES ('KSSHEL', 'Kerner-Scott Women''s
Shelter','HOUSING', null, null);
INSERT INTO l_desc_project VALUES ('LYON', 'The Lyon
Building','HOUSING', true, true);
INSERT INTO l_desc_project VALUES ('MEDICAL', 'Medical
Staff','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('MORR', 'The Morrison','HOUSING',
true, true);
INSERT INTO l_desc_project VALUES ('SAGE', 'SAGE Program','CLINICAL',
null, null);
INSERT INTO l_desc_project VALUES ('SHELTER', 'Shelter
Program','HOUSING', null, null);
INSERT INTO l_desc_project VALUES ('SUPPORT', 'Administrative
Support','ADMIN', null, null);
INSERT INTO l_desc_project VALUES ('UNION', 'The Union Hotel','HOUSING',
true, true);
INSERT INTO l_desc_project VALUES ('SCATTERED', 'Scattered Site
Housing','HOUSING', false, false);
INSERT INTO l_desc_project VALUES ('LEASED', 'Scattered Site
(Leased)','HOUSING', false, true);
If you comment out all those "INSERT INTO ..." lines, and then add your
own (obviously changing the description), your new database will be
created with only those 2 projects available:
INSERT INTO l_desc_project VALUES ('VETS', 'A more readable description
goes here','HOUSING', true, true);
INSERT INTO l_desc_project VALUES ('CASCADE', 'A more readable
description goes here','HOUSING', true, true);
(you'll need to decide about auto-calculating subsidies and rents, but
that's what those last 2 values are all about)
So to summarize, I would recommend playing around on the Admin page to
see what effect the values in the lookup tables have, and then see what
you can do with the config files.
-Jonathan
|
|
From: Jonathan H. <jhe...@de...> - 2006-11-28 18:42:30
|
Nicholas Burmeister wrote:
> I do believe we've finished with the tables that we needed. I guess now we need to go ahead and customise things a bit for Compass Center. I noticed in one of our emails that some things can be edited directly from within Chasers administration. So there I went, all eager to edit something! And behold, a spam of errors occured after Client Unduplication and before Update Chasers from Shamis:
>
> Warning: filemtime() [function.filemtime]: stat failed for /shared/is/mh45/ma-dal.db in /var/www/html/chasers/chasers_admin.php on line 163
>
> Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation "clin_dal" does not exist in /var/www/html/chasers/sql_layer.php on line 30
>
> Warning: pg_fetch_array() expects parameter 1 to be resource, boolean given in /var/www/html/chasers/sql_layer.php on line 448
>
> Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation "clin_tauth" does not exist in /var/www/html/chasers/sql_layer.php on line 30
>
> Warning: pg_fetch_array() expects parameter 1 to be resource, boolean given in /var/www/html/chasers/sql_layer.php on line 448
>
> Are you interested in addressing this now,
You should be able to comment these out in chasers_admin.php.
> or do you want to go ahead and teach me how to remove DESC specific stuff and add the Compass Center stuff that we know will be needed, such as housing sites that are know (Vets, Cascade, etc)?
>
The best place to start customizing CHASERS is probably in the lookup
tables, and in the config files located in the config directory. You've
already done a bit with the config files (changing data_type to phone
for the contact_information records, adding child records to
config_client.php etc).
For example, to change the "DESC residence" to something else, you would
change these two lines in config/config_residence_desc.php:
'singular'=>'DESC Residence',
'plural'=>'DESC Residencies',
For more on config file options, take a look at the config file section
of the CHASERS engine documentation:
http://www.desc.org/chasers_wiki/index.php/Engine_Documentation:_Configuration_File_Options_for_Engine
If you go to the CHASERS Admin page and click the link that reads "List
all DB tables", you'll get a list of all the tables in the database. The
ones that start with "l_" are lookup tables. These tables contain the
values that appear on the various drop lists you are presented with when
you add records to CHASERS.
For example, if you want to get rid of the Morrison, Kerner-Scott House,
etc, find the link to the table "l_desc_project". This table contains a
list of all the DESC projects. If you delete these records, and then add
Vets and Cascade, you'll be able to add units to housing_unit for these
projects, and then move people into those units.
Note: since you have most likely already added data to the test database
that references l_desc_project, you probably won't be able to delete all
the DESC-specific records in this table.
Using the admin page is fine for testing and tweaking an existing
installation, but while you are doing so, keep in mind that the files
that initially populates these lookups are in database/pg/client and can
be changed there if you want the effects to be included when you create
the live database.
To continue the example from above, create.l_desc_project.sql looks like
this:
CREATE TABLE l_desc_project (
desc_project_code VARCHAR(10) PRIMARY KEY,
description VARCHAR(80) NOT NULL UNIQUE,
desc_program_code VARCHAR(10) NOT NULL REFERENCES
l_desc_program (desc_program_code),
auto_calculate_subsidy_charges BOOLEAN,
auto_calculate_rent_charges BOOLEAN
);
INSERT INTO l_desc_project VALUES ('KSH', 'Kerner-Scott
House','HOUSING', true, true);
INSERT INTO l_desc_project VALUES ('ACCOUNT', 'Accounting','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('ALL', '(For the E.D.)','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('CD', 'Chemical Dependency
Program','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('CLINADMIN', 'Clinical
Administration','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('CRP', 'Crisis Respite
Program','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('DEVEL', 'Fund Development','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('FACIL', 'Facilities','ADMIN', null,
null);
INSERT INTO l_desc_project VALUES ('HCH', 'Health Care for the
Homeless','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('HOST', 'HOST Program','CLINICAL',
null, null);
INSERT INTO l_desc_project VALUES ('HOUSADMIN', 'Housing
Administration','ADMIN', null, null);
INSERT INTO l_desc_project VALUES ('HOUSONCALL', 'Housing On-Call
(multiple projects)','HOUSING', null, null);
INSERT INTO l_desc_project VALUES ('IR', 'Information &
Referral','ADMIN', null, null);
INSERT INTO l_desc_project VALUES ('IS', 'Information Services','ADMIN',
null, null);
INSERT INTO l_desc_project VALUES ('HEET', 'HEET Program','HOUSING',
null, null);
INSERT INTO l_desc_project VALUES ('KSSHEL', 'Kerner-Scott Women''s
Shelter','HOUSING', null, null);
INSERT INTO l_desc_project VALUES ('LYON', 'The Lyon
Building','HOUSING', true, true);
INSERT INTO l_desc_project VALUES ('MEDICAL', 'Medical
Staff','CLINICAL', null, null);
INSERT INTO l_desc_project VALUES ('MORR', 'The Morrison','HOUSING',
true, true);
INSERT INTO l_desc_project VALUES ('SAGE', 'SAGE Program','CLINICAL',
null, null);
INSERT INTO l_desc_project VALUES ('SHELTER', 'Shelter
Program','HOUSING', null, null);
INSERT INTO l_desc_project VALUES ('SUPPORT', 'Administrative
Support','ADMIN', null, null);
INSERT INTO l_desc_project VALUES ('UNION', 'The Union Hotel','HOUSING',
true, true);
INSERT INTO l_desc_project VALUES ('SCATTERED', 'Scattered Site
Housing','HOUSING', false, false);
INSERT INTO l_desc_project VALUES ('LEASED', 'Scattered Site
(Leased)','HOUSING', false, true);
If you comment out all those "INSERT INTO ..." lines, and then add your
own (obviously changing the description), your new database will be
created with only those 2 projects available:
INSERT INTO l_desc_project VALUES ('VETS', 'A more readable description
goes here','HOUSING', true, true);
INSERT INTO l_desc_project VALUES ('CASCADE', 'A more readable
description goes here','HOUSING', true, true);
(you'll need to decide about auto-calculating subsidies and rents, but
that's what those last 2 values are all about)
So to summarize, I would recommend playing around on the Admin page to
see what effect the values in the lookup tables have, and then see what
you can do with the config files.
-Jonathan
|
|
From: Jonathan H. <jhe...@de...> - 2006-11-28 18:19:19
|
Hey Nicholas, Sorry for the delay--I'd meant to respond to your last email last week sometime (I'll respond to it separately now). Regarding database size, ours is about 225 megs compressed (for backups) and the total diskspace used by Postgres for the database is just over 3 gigs. Any modern hard drive should be adequate as far as size is concerned. However, I would recommend going with a RAID setup for data integrity. You'll also want to figure out how you are going to handle backups, since you never want to lose any data once people start using the system. We back the db up every 2 hours to a separate server, then place one of these backups onto a tape each night. -Jonathan Nicholas Burmeister wrote: > Hey Jon, > > Just wondering where we're at with Chasers. I'm also wondering if you > could give me some sort of estimate of how large your database is, > since we're thinking of buying a server for Chasers, and we're > wondering about disk space. We could go with SCSI drives for less > space, or so SATA for more; I prefer SCSI if the database space needs > aren't going to be too large. > > Thanks! > > > Nicholas Burmeister > IT Department > The Compass Center > 206-357-3144 > nbu...@co... <mailto:nbu...@co...> > |
|
From: Nicholas B. <nbu...@co...> - 2006-11-16 00:00:49
|
I do believe we've finished with the tables that we needed. I guess now = we need to go ahead and customise things a bit for Compass Center. I = noticed in one of our emails that some things can be edited directly = from within Chasers administration. So there I went, all eager to edit = something! And behold, a spam of errors occured after Client = Unduplication and before Update Chasers from Shamis: =20 Warning: filemtime() [function.filemtime]: stat failed for = /shared/is/mh45/ma-dal.db in /var/www/html/chasers/chasers_admin.php on = line 163 Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation = "clin_dal" does not exist in /var/www/html/chasers/sql_layer.php on line = 30 Warning: pg_fetch_array() expects parameter 1 to be resource, boolean = given in /var/www/html/chasers/sql_layer.php on line 448 Warning: pg_query() [function.pg-query]: Query failed: ERROR: relation = "clin_tauth" does not exist in /var/www/html/chasers/sql_layer.php on = line 30 Warning: pg_fetch_array() expects parameter 1 to be resource, boolean = given in /var/www/html/chasers/sql_layer.php on line 448 Are you interested in addressing this now, or do you want to go ahead = and teach me how to remove DESC specific stuff and add the Compass = Center stuff that we know will be needed, such as housing sites that are = know (Vets, Cascade, etc)? =20 =20 Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... =20 ________________________________ From: cha...@li... on behalf of = Nicholas Burmeister Sent: Wed 11/15/2006 3:43 PM To: general Subject: RE: [Chasers-general] CD Tables Boy do I feel like a dork, all over a single letter missing! Yep, = created the lookup table, updated array, and presto, it works just fine. =20 Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... =20 ________________________________ From: cha...@li... on behalf of = Jonathan Hedstrom Sent: Wed 11/15/2006 3:03 PM To: general Subject: Re: [Chasers-general] CD Tables Nicholas Burmeister wrote: > Ok, let's start over! >=20 > If I understand correctly, you're saying that the reason the add cd = service fails is because I didn't run create.view.service_cd.sql. I'm = pretty sure I did, so I compared my create.view.service_cd.sql with what = you said needed to be in there: >=20 > CREATE OR REPLACE VIEW l_service_cd AS > SELECT service_code AS service_cd_code, > description > FROM l_service WHERE is_current AND used_by_cd; > > =20 I see now. Sorry to confuse. The above code goes in a file called create.view.l_service_cd.sql (note the "l_"). This is different from create.view.service_cd.sql -Jonathan |
|
From: Nicholas B. <nbu...@co...> - 2006-11-15 23:45:11
|
Boy do I feel like a dork, all over a single letter missing! Yep, = created the lookup table, updated array, and presto, it works just fine. =20 Nicholas Burmeister IT Department The Compass Center 206-357-3144 nbu...@co... =20 ________________________________ From: cha...@li... on behalf of = Jonathan Hedstrom Sent: Wed 11/15/2006 3:03 PM To: general Subject: Re: [Chasers-general] CD Tables Nicholas Burmeister wrote: > Ok, let's start over! >=20 > If I understand correctly, you're saying that the reason the add cd = service fails is because I didn't run create.view.service_cd.sql. I'm = pretty sure I did, so I compared my create.view.service_cd.sql with what = you said needed to be in there: >=20 > CREATE OR REPLACE VIEW l_service_cd AS > SELECT service_code AS service_cd_code, > description > FROM l_service WHERE is_current AND used_by_cd; > > =20 I see now. Sorry to confuse. The above code goes in a file called create.view.l_service_cd.sql (note the "l_"). This is different from create.view.service_cd.sql -Jonathan |
|
From: Jonathan H. <jhe...@de...> - 2006-11-15 23:03:48
|
Nicholas Burmeister wrote: > Ok, let's start over! > > If I understand correctly, you're saying that the reason the add cd service fails is because I didn't run create.view.service_cd.sql. I'm pretty sure I did, so I compared my create.view.service_cd.sql with what you said needed to be in there: > > CREATE OR REPLACE VIEW l_service_cd AS > SELECT service_code AS service_cd_code, > description > FROM l_service WHERE is_current AND used_by_cd; > > I see now. Sorry to confuse. The above code goes in a file called create.view.l_service_cd.sql (note the "l_"). This is different from create.view.service_cd.sql -Jonathan |
1 message has been excluded from this view by a project administrator.
