/var/lib/gnumed/server/sql/gmDemographics-Person-views.sql is in gnumed-server 16.17-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 | -- project: GNUmed
-- purpose: views for easier identity access
-- author: Karsten Hilbert
-- license: GPL v2 or later (details at http://gnu.org)
-- $Source: /home/ncq/Projekte/cvs2git/vcs-mirror/gnumed/gnumed/server/sql/gmDemographics-Person-views.sql,v $
-- $Id: gmDemographics-Person-views.sql,v 1.55 2006-08-04 05:40:27 ncq Exp $
-- ==========================================================
\unset ON_ERROR_STOP
drop index dem.idx_identity_dob;
drop index dem.idx_names_last_first;
drop index dem.idx_names_firstnames;
\set ON_ERROR_STOP 1
create index idx_identity_dob on dem.identity(dob);
create index idx_names_last_first on dem.names(lastnames, firstnames);
-- need this for queries on "first" only - becomes redundant with PG 8.0
create index idx_names_firstnames on dem.names(firstnames);
-- ==========================================================
-- rules/triggers/functions on table "names"
-- allow only unique names
\unset ON_ERROR_STOP
drop index dem.idx_uniq_act_name;
create unique index idx_uniq_act_name on dem.names(id_identity) where active = true;
\set ON_ERROR_STOP 1
-- IH: 9/3/02
-- trigger function to ensure only one name is active
-- it's behaviour is to set all other names to inactive when
-- a name is made active
\unset ON_ERROR_STOP
drop trigger tr_uniq_active_name on dem.names;
drop function dem.f_uniq_active_name();
drop trigger tr_always_active_name on dem.names;
drop function dem.f_always_active_name();
\set ON_ERROR_STOP 1
-- do not allow multiple active names per person
create or replace function dem.f_uniq_active_name() RETURNS trigger AS '
DECLARE
-- tmp text;
BEGIN
-- tmp := ''identity:'' || NEW.id_identity || '',id:'' || NEW.id || '',name:'' || NEW.firstnames || '' '' || NEW.lastnames;
-- raise notice ''uniq_active_name: [%]'', tmp;
if NEW.active = true then
update dem.names set active = false
where
id_identity = NEW.id_identity
and
active = true;
end if;
return NEW;
END;' LANGUAGE 'plpgsql';
--create TRIGGER tr_uniq_active_name
-- BEFORE insert on dem.names
-- FOR EACH ROW EXECUTE PROCEDURE dem.F_uniq_active_name();
-- ensure we always have an active name
create or replace function dem.f_always_active_name() returns trigger as '
BEGIN
if NEW.active = false then
raise exception ''Cannot delete/disable active name. Another name must be activated first.'';
return OLD;
end if;
return NEW;
END;
' language 'plpgsql';
--create trigger tr_always_active_name
-- before update or delete on dem.names
-- for each row execute PROCEDURE dem.f_always_active_name();
-- FIXME: we don't actually want this to be available
\unset ON_ERROR_STOP
drop trigger TR_delete_names on dem.identity;
drop function dem.F_delete_names();
\set ON_ERROR_STOP 1
create or replace function dem.f_delete_names() RETURNS trigger AS '
DECLARE
BEGIN
DELETE from dem.names WHERE id_identity=OLD.id;
RETURN OLD;
END;' LANGUAGE 'plpgsql';
-- only re-enable this once we know how to do it !!
--CREATE TRIGGER TR_delete_names
-- BEFORE DELETE on dem.identity
-- FOR EACH ROW EXECUTE PROCEDURE dem.F_delete_names();
-- business functions
create or replace function dem.add_name(integer, text, text, bool) returns integer as '
DECLARE
_id_identity alias for $1;
_first alias for $2;
_last alias for $3;
_active alias for $4;
_id integer;
BEGIN
-- deactivate all the existing names if this name is to become active
if _active then
update dem.names set active = false where id_identity = _id_identity;
end if;
-- name already there for this identity ?
select into _id id from dem.names where id_identity = _id_identity and firstnames = _first and lastnames = _last;
if FOUND then
update dem.names set active = _active where id = _id;
return _id;
end if;
-- no, insert new name
insert into dem.names (id_identity, firstnames, lastnames, active) values (_id_identity, _first, _last, _active);
if FOUND then
return currval(''dem.names_id_seq'');
end if;
return NULL;
END;' language 'plpgsql';
create or replace function dem.set_nickname(integer, text) returns integer as '
DECLARE
_id_identity alias for $1;
_nick alias for $2;
_names_row record;
msg text;
BEGIN
-- 0.1: Just always set the nickname inside the active name
-- post 0.1: openEHR-like (name: pk, fk_identity, name, fk_type, comment, is_legal, is_active ...)
-- does name exist ?
select into _names_row * from dem.names where id_identity = _id_identity and active = true;
if not found then
msg := ''Cannot set nickname ['' || _nick || '']. No active <names> row with id_identity ['' || _id_identity || ''] found.'';
raise exception ''%'', msg;
end if;
update dem.names set preferred = _nick where id = _names_row.id;
return _names_row.id;
END;' language 'plpgsql';
comment on function dem.set_nickname(integer, text) is
'Setting the nickname only makes sense for the currently active\n
name. However, we also want to keep track of previous nicknames.\n
Hence we would set the nickname right in the active name if\n
it is NULL. It it contains a previous nickname (eg IS NOT NULL)\n
we will inactivate the currently active name and copy it into\n
a new active name but with the nickname set to the new one.\n
Unsetting works the same (IOW *setting* to NULL).';
-- ==========================================================
create or replace function dem.create_occupation(text) RETURNS integer AS '
DECLARE
_job alias for $1;
_id integer;
BEGIN
select into _id id from dem.occupation where name = _job;
if FOUND then
return _id;
end if;
insert into dem.occupation (name) values (_job);
return currval(''dem.occupation_id_seq'');
END;' LANGUAGE 'plpgsql';
-- ==========================================================
create or replace function dem.link_person_comm(integer, text, text, bool) RETURNS integer AS '
DECLARE
_id_identity alias for $1;
_comm_medium alias for $2;
_url alias for $3;
_is_confidential alias for $4;
_id_comm_type integer;
_id_lnk_identity2comm integer;
msg text;
BEGIN
-- FIXME: maybe need to update is_confidential
SELECT INTO _id_lnk_identity2comm id from dem.lnk_identity2comm WHERE id_identity = _id_identity AND url ILIKE _url;
IF FOUND THEN
RETURN _id_lnk_identity2comm;
END IF;
-- does comm_medium exist ?
SELECT INTO _id_comm_type id from dem.enum_comm_types WHERE description ILIKE _comm_medium;
IF NOT FOUND THEN
msg := ''Cannot set person comm ['' || _id_identity || '', '' || _comm_medium || '','' || _url || '']. No enum_comms_types row with description ['' || _comm_medium || ''] found.'';
RAISE EXCEPTION ''---> %'', msg;
END IF;
-- update existing comm. 0.1 Release (FIXME: rewrite later to allow for any number of type entries per identity)
SELECT INTO _id_lnk_identity2comm id from dem.lnk_identity2comm WHERE id_identity = _id_identity AND id_type = _id_comm_type;
IF FOUND THEN
UPDATE dem.lnk_identity2comm SET url = _url, is_confidential = _is_confidential WHERE id = _id_lnk_identity2comm;
RETURN _id_lnk_identity2comm;
END IF;
-- create new communication2identity link
INSERT INTO dem.lnk_identity2comm (id_identity, url, id_type, is_confidential) values (_id_identity, _url, _id_comm_type, _is_confidential);
RETURN currval(''dem.lnk_identity2comm_id_seq'');
END;' LANGUAGE 'plpgsql';
\unset ON_ERROR_STOP
drop function dem.new_pupic() cascade;
\set ON_ERROR_STOP 1
create or replace function dem.new_pupic() RETURNS char(24) AS '
DECLARE
BEGIN
-- how does this work? How do we get new ''unique'' numbers?
RETURN ''0000000000'';
END;' LANGUAGE 'plpgsql';
-- ==========================================================
\unset ON_ERROR_STOP
drop view dem.v_gender_labels;
\set ON_ERROR_STOP 1
create view dem.v_gender_labels as
select
gl.tag,
_(gl.tag) as l10n_tag,
gl.label,
_(gl.label) as l10n_label,
gl.comment,
gl.sort_weight as sort_weight,
gl.pk as pk_gender_label
from
dem.gender_label gl
;
-- ==========================================================
\unset ON_ERROR_STOP
drop view dem.v_basic_person cascade;
\set ON_ERROR_STOP 1
create view dem.v_basic_person as
select
i.pk as pk_identity,
n.id as n_id,
i.title as title,
n.firstnames as firstnames,
n.lastnames as lastnames,
i.dob as dob,
i.cob as cob,
i.gender as gender,
_(i.gender) as l10n_gender,
i.karyotype as karyotype,
i.pupic as pupic,
case when i.fk_marital_status is null
then 'unknown'
else (select ms.name from dem.marital_status ms, dem.identity i1 where ms.pk=i.fk_marital_status and i1.pk=i.pk)
end as marital_status,
case when i.fk_marital_status is null
then _('unknown')
else (select _(ms1.name) from dem.marital_status ms1, dem.identity i1 where ms1.pk=i.fk_marital_status and i1.pk=i.pk)
end as l10n_marital_status,
i.fk_marital_status as pk_marital_status,
n.preferred as preferred,
i.xmin as xmin_identity
from
dem.identity i,
dem.names n
where
i.deleted is False and
i.deceased is NULL and
n.active = true and
n.id_identity = i.pk
;
-- ----------------------------------------------------------
-- create new name and new identity
create RULE r_insert_basic_person AS
ON INSERT TO dem.v_basic_person DO INSTEAD (
INSERT INTO dem.identity (pupic, gender, dob, cob, title)
values (dem.new_pupic(), NEW.gender, NEW.dob, NEW.cob, NEW.title);
INSERT INTO dem.names (firstnames, lastnames, id_identity)
VALUES (NEW.firstnames, NEW.lastnames, currval('dem.identity_pk_seq'));
)
;
-- rule for name change - add new name to list, making it active
create RULE r_update_basic_person1 AS
ON UPDATE TO dem.v_basic_person WHERE
NEW.firstnames != OLD.firstnames OR
NEW.lastnames != OLD.lastnames OR
NEW.title != OLD.title
DO INSTEAD
INSERT INTO dem.names (firstnames, lastnames, id_identity, active)
VALUES (NEW.firstnames, NEW.lastnames, NEW.pk_identity, true);
-- rule for identity change
-- yes, you would use this, think carefully.....
create RULE r_update_basic_person2 AS
ON UPDATE TO dem.v_basic_person DO INSTEAD
UPDATE dem.identity SET
dob=NEW.dob,
cob=NEW.cob,
gender=NEW.gender
WHERE pk=NEW.pk_identity;
create RULE r_delete_basic_person AS
ON DELETE to dem.v_basic_person DO INSTEAD
update dem.identity set deleted = True where pk = OLD.pk_identity;
create rule r_del_identity as
on delete to dem.identity do instead
update dem.identity set deleted = True where pk = OLD.pk;
-- =============================================
-- staff views
\unset ON_ERROR_STOP
drop view dem.v_staff;
\set ON_ERROR_STOP 1
create view dem.v_staff as
select
vbp.pk_identity as pk_identity,
s.pk as pk_staff,
vbp.title as title,
vbp.firstnames as firstnames,
vbp.lastnames as lastnames,
s.short_alias as short_alias,
_(sr.name) as role,
vbp.dob as dob,
vbp.gender as gender,
s.db_user as db_user,
s.comment as comment,
s.is_active as is_active,
(select (
select exists (
SELECT 1
from pg_group
where
(SELECT usesysid from pg_user where usename = s.db_user) = any(grolist) and
groname=current_database()
)
) AND (
select exists (
SELECT 1
from pg_group
where
(SELECT usesysid from pg_user where usename = s.db_user) = any(grolist) and
groname='gm-logins'
)
)) as can_login,
s.xmin as xmin_staff,
s.fk_role as pk_role
from
dem.staff s,
dem.staff_role sr,
dem.v_basic_person vbp
where
s.fk_role = sr.pk
and
s.fk_identity = vbp.pk_identity
;
-- =========================================================
-- emulate previous structure of address linktables
\unset ON_ERROR_STOP
drop view dem.lnk_person2address;
drop view dem.lnk_org2address;
\set ON_ERROR_STOP 1
CREATE VIEW dem.lnk_person2address AS
SELECT id_identity, id_address, id_type
from dem.lnk_person_org_address;
CREATE VIEW dem.lnk_org2address AS
SELECT id_org, id_address
from dem.lnk_person_org_address;
-- ==========================================================
\unset ON_ERROR_STOP
drop view dem.v_person_comms_flat cascade;
\set ON_ERROR_STOP 1
create view dem.v_person_comms_flat as
select
pk,
v1.email ,
v2.fax,
v3.homephone,
v4.workphone,
v5.mobile
from
(select pk from dem.identity) as i
left outer join
(select url as email, id_identity from dem.lnk_identity2comm where id_type =1) as v1
on (pk = v1.id_identity)
full outer join
(select url as fax, id_identity as id_id_fax from dem.lnk_identity2comm where id_type =2 ) as v2
on (pk = v2.id_id_fax)
full outer join
(select url as homephone, id_identity as id_id_homephone from dem.lnk_identity2comm where id_type =3 ) as v3
on (pk = v3.id_id_homephone)
full outer join
(select url as workphone, id_identity as id_id_workphone from dem.lnk_identity2comm where id_type =4 ) as v4
on (pk = v4.id_id_workphone)
full outer join
(select url as mobile, id_identity as id_id_mobile from dem.lnk_identity2comm where id_type =5 ) as v5
on (pk = v5.id_id_mobile);
-- =========================================================
-- ==========================================================
\unset ON_ERROR_STOP
drop index dem.idx_lnk_pers2rel;
\set ON_ERROR_STOP 1
create index idx_lnk_pers2rel on dem.lnk_person2relative(id_identity, id_relation_type);
-- consider regular "CLUSTER idx_lnk_pers2rel on dem.lnk_person2relative;"
-- ==========================================================
-- permissions
-- ==========================================================
GRANT SELECT ON
dem.v_staff
, dem.lnk_person2address
, dem.lnk_org2address
, dem.v_person_comms_flat
, dem.v_gender_labels
TO GROUP "gm-doctors";
GRANT SELECT, INSERT, UPDATE, DELETE ON
dem.v_basic_person
TO GROUP "gm-doctors";
-- =============================================
-- do simple schema revision tracking
delete from gm_schema_revision where filename = '$RCSfile: gmDemographics-Person-views.sql,v $';
INSERT INTO gm_schema_revision (filename, version) VALUES('$RCSfile: gmDemographics-Person-views.sql,v $', '$Revision: 1.55 $');
-- =============================================
-- $Log: gmDemographics-Person-views.sql,v $
-- Revision 1.55 2006-08-04 05:40:27 ncq
-- - dem.identity has pk, not pk_identity so fix rule
--
-- Revision 1.54 2006/07/27 17:12:42 ncq
-- - add .deleted to dem.identity so we can mark patients as deleted
-- - exclude .deleted patients from v_basic_person
-- - add RULEs to set deleted=True on delete to identity
--
-- Revision 1.53 2006/06/09 14:44:21 ncq
-- - cleanup
-- - add dem.v_staff.can_login
--
-- Revision 1.52 2006/06/06 20:58:29 ncq
-- - add dem.staff.is_active and propagate it
--
-- Revision 1.51 2006/05/12 12:19:56 ncq
-- - add fields to dem.v_staff
--
-- Revision 1.50 2006/01/23 22:10:57 ncq
-- - staff.sign -> .short_alias
--
-- Revision 1.49 2006/01/22 20:36:43 ncq
-- - fix add_name()
--
-- Revision 1.48 2006/01/11 22:31:39 ncq
-- - fix another error in set_nickname()
--
-- Revision 1.47 2006/01/11 13:20:31 ncq
-- - add missing ;
--
-- Revision 1.46 2006/01/06 10:12:02 ncq
-- - add missing grants
-- - add_table_for_audit() now in "audit" schema
-- - demographics now in "dem" schema
-- - add view v_inds4vaccine
-- - move staff_role from clinical into demographics
-- - put add_coded_term() into "clin" schema
-- - put German things into "de_de" schema
--
-- Revision 1.45 2006/01/01 20:39:22 ncq
-- - cleanup
--
-- Revision 1.44 2005/12/08 16:13:13 ncq
-- - need to declare plpgsql variables
--
-- Revision 1.43 2005/12/07 16:28:54 ncq
-- - some tightening of column scopes
--
-- Revision 1.42 2005/12/06 13:22:50 ncq
-- - add missing : in front of =
--
-- Revision 1.41 2005/09/19 16:38:51 ncq
-- - adjust to removed is_core from gm_schema_revision
--
-- Revision 1.40 2005/07/14 21:31:42 ncq
-- - partially use improved schema revision tracking
--
-- Revision 1.39 2005/06/10 07:21:05 ncq
-- - add v_basic_person.l10n_gender
--
-- Revision 1.38 2005/05/24 19:54:47 ncq
-- - create_person_comm() -> link_person_comm() with some caveat for post-0.1
--
-- Revision 1.37 2005/05/22 21:44:22 cfmoro
-- For 0.1, update set nickname inside the active name
--
-- Revision 1.36 2005/04/24 14:53:51 ncq
-- - add create_person_comm from Carlos
--
-- Revision 1.35 2005/04/20 16:04:58 ncq
-- - 7.1 did not like _name for some strange reason, make it _job
--
-- Revision 1.34 2005/04/17 16:36:45 ncq
-- - improve add_name()
-- - add set_nickname()
-- - improve create_occupation()
--
-- Revision 1.33 2005/04/14 17:45:21 ncq
-- - gender_label.sort_rank -> sort_weight
--
-- Revision 1.32 2005/04/14 16:57:00 ncq
-- - typo fix
--
-- Revision 1.31 2005/02/13 14:41:52 ncq
-- - v_basic_person.i_pk was an exceptionally bad choice, make that pk_identity
-- - remove legacy identity.pk mappings in v_basic_person
--
-- Revision 1.30 2005/02/12 13:49:14 ncq
-- - identity.id -> identity.pk
-- - allow NULL for identity.fk_marital_status
-- - subsequent schema changes
--
-- Revision 1.29 2005/02/02 09:53:01 sjtan
--
-- keep em happy.
--
-- Revision 1.28 2005/01/26 21:29:11 ncq
-- - added missing GRANT
--
-- Revision 1.27 2004/12/21 09:59:40 ncq
-- - comm_channel -> comm else too long on server < 7.3
--
-- Revision 1.26 2004/12/20 19:04:37 ncq
-- - fixes by Ian while overhauling the demographics API
--
-- Revision 1.25 2004/12/15 09:30:48 ncq
-- - correctly pull in martial status in v_basic_person
-- (update/insert rules may be lacking now, though ?)
--
-- Revision 1.24 2004/12/15 04:18:03 ihaywood
-- minor changes
-- pointless irregularity in v_basic_address
-- extended v_basic_person to more fields.
--
-- Revision 1.23 2004/10/19 23:27:11 sjtan
-- this came up as script stopping bug , when run inside a in-order
-- concatenated monolithic sql script.
--
-- Revision 1.22 2004/08/16 19:35:52 ncq
-- - added idx_lnk_pers2rel based on ideas by Aldfaer (Anne v.d.Ploeg)
--
-- Revision 1.21 2004/07/20 07:19:12 ncq
-- - in add_name() only deactivate existing names if new name is to be active
-- or else we'd be able to have patients without an active name ...
--
-- Revision 1.20 2004/07/20 01:01:46 ihaywood
-- changing a patients name works again.
-- Name searching has been changed to query on names rather than v_basic_person.
-- This is so the old (inactive) names are still visible to the search.
-- This is so when Mary Smith gets married, we can still find her under Smith.
-- [In Australia this odd tradition is still the norm, even female doctors
-- have their medical registration documents updated]
--
-- SOAPTextCtrl now has popups, but the cursor vanishes (?)
--
-- Revision 1.19 2004/07/17 20:57:53 ncq
-- - don't use user/_user workaround anymore as we dropped supporting
-- it (but we did NOT drop supporting readonly connections on > 7.3)
--
-- Revision 1.18 2004/06/28 12:16:19 ncq
-- - drop ... cascade; doesn't work on 7.1
--
-- Revision 1.17 2004/06/27 02:39:46 sjtan
--
-- fix-up for lots of empty rows.
--
-- Revision 1.16 2004/06/25 15:19:42 ncq
-- - add v_person_comms_flat by Syan, this isn't really
-- nice since it uses hardcoded comm types
--
-- Revision 1.15 2004/06/25 15:08:57 ncq
-- - v_pat_comms by Syan
--
-- Revision 1.14 2004/04/07 18:16:06 ncq
-- - move grants into re-runnable scripts
-- - update *.conf accordingly
--
-- Revision 1.13 2004/03/27 18:35:56 ncq
-- - cleanup
--
-- Revision 1.12 2004/03/27 04:37:01 ihaywood
-- lnk_person2address now lnk_person_org_address
-- sundry bugfixes
--
-- Revision 1.11 2003/12/29 15:35:15 uid66147
-- - staff views and grants
--
-- Revision 1.10 2003/12/02 02:14:40 ncq
-- - comment out triggers on name.active until we know how to to them :-(
-- - at least we CAN do active names now
-- - ensure unique active name by means of an index, though
--
-- Revision 1.9 2003/12/01 22:11:26 ncq
-- - remove a raise notice
--
-- Revision 1.8 2003/11/26 23:54:51 ncq
-- - lnk_vaccdef2reg does not exist anymore
--
-- Revision 1.7 2003/11/23 23:37:09 ncq
-- - names.title -> identity.title
-- - yet another go at uniq_active_name triggers
--
-- Revision 1.6 2003/11/23 14:05:38 sjtan
--
-- slight debugging of add_names: start off with active=false, and then other attributes won't be affected
-- by trigger side effects.
--
-- Revision 1.5 2003/11/23 12:53:20 sjtan
-- *** empty log message ***
--
-- Revision 1.4 2003/11/23 00:02:47 sjtan
--
-- NEW.active is not the same as NEW.active = true; does it mean 'is there a NEW.active' ?
-- the syntax for n_id variable didn't seem to work; this works?
--
-- Revision 1.3 2003/11/22 13:58:25 ncq
-- - rename constraint for unique active names
-- - add add_name() function
--
-- Revision 1.2 2003/10/19 13:01:20 ncq
-- - add omitted "index"
--
-- Revision 1.1 2003/08/02 10:46:03 ncq
-- - rename schema files by service
--
-- Revision 1.2 2003/05/12 12:43:39 ncq
-- - gmI18N, gmServices and gmSchemaRevision are imported globally at the
-- database level now, don't include them in individual schema file anymore
--
-- Revision 1.1 2003/04/18 13:17:38 ncq
-- - collect views for Identity DB here
--
|