Skip to Content

Changes for page Data Structures

Last modified by Kerem Yollu on 2025/03/23 11:28
From version 5.2
edited by Kerem Yollu
on 2025/03/21 16:08
Change comment: There is no comment for this version
To version 1.1
edited by Kerem Yollu
on 2025/03/21 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -xwiki:Kynsight.Projects.KPM.Data Structures.Data Structure And Models.WebHome
1 +Kynsight.Projects.KPM.Data Structure And Models.WebHome
Content
... ... @@ -3,24 +3,23 @@
3 3  
4 4  = Models =
5 5  
6 -* (((
7 7  == Address ==
8 -)))
9 -** {{code language="sql" layout="LINENUMBERS"}}DROP TABLE IF EXISTS public.address;
10 10  
8 +DROP TABLE IF EXISTS public.address;
9 +
11 11  CREATE TABLE public.address
12 12  (
13 13   uid SERIAL PRIMARY KEY,
14 - country CHAR(2) NOT NULL, -- ISO 3166-1 alpha-2 (e.g., 'CH')
15 - region VARCHAR(100), -- State or canton
13 + country CHAR(2) NOT NULL,              ~-~- ISO 3166-1 alpha-2 (e.g., 'CH')
14 + region VARCHAR(100),                   ~-~- State or canton
16 16   city VARCHAR(100) NOT NULL,
17 17   postcode VARCHAR(20) NOT NULL,
18 18   street VARCHAR(255) NOT NULL,
19 - number VARCHAR(20),
20 - unit VARCHAR(50), -- Apartment/Suite/Floor/etc.
21 - extra_address VARCHAR(255), -- Additional info
22 - lon DOUBLE PRECISION, -- Longitude (optional)
23 - lat DOUBLE PRECISION -- Latitude (optional)
18 + number VARCHAR(20),          
19 + unit VARCHAR(50),                      ~-~- Apartment/Suite/Floor/etc.
20 + extra_address VARCHAR(255),            ~-~- Additional info
21 + lon DOUBLE PRECISION,                  ~-~- Longitude (optional)
22 + lat DOUBLE PRECISION                   ~-~- Latitude (optional)
24 24  )
25 25  
26 26  TABLESPACE pg_default;
... ... @@ -29,49 +29,4 @@
29 29   OWNER to kpm_rw;
30 30  
31 31  COMMENT ON TABLE public.address
32 - IS 'addresses table, instead of making use of addresses for ever company, customer and co... Prefer to make addresses table and then assign it to a company or a user etc.';{{/code}}
33 -
34 -
35 -
36 -* (((
37 -== Company_Type ==
38 -)))
39 -** {{code language="sql"}}-- Table: public.company_type
40 -
41 --- DROP TABLE IF EXISTS public.company_type;
42 -
43 -CREATE TABLE IF NOT EXISTS public.company_type
44 -(
45 - uid SERIAL PRIMARY KEY,
46 - name VARCHAR(100) COLLATE pg_catalog."default" NOT NULL,
47 - description VARCHAR(255) COLLATE pg_catalog."default",
48 - creation_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
49 - updated_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP
50 -)
51 -TABLESPACE pg_default;
52 -
53 -ALTER TABLE IF EXISTS public.company_type
54 - OWNER TO kpm_rw;
55 -
56 -COMMENT ON TABLE public.company_type
57 - IS 'Reference table for different types of companies (e.g., manufacturer, distributor, partner, etc.). Used by company table.';
58 -
59 -COMMENT ON COLUMN public.company_type.uid
60 - IS 'Unique ID for each company type';
61 -
62 -COMMENT ON COLUMN public.company_type.name
63 - IS 'Short name of the company type (e.g., Manufacturer, EMS, Partner)';
64 -
65 -COMMENT ON COLUMN public.company_type.description
66 - IS 'Optional longer description of the company type';
67 -
68 -COMMENT ON COLUMN public.company_type.creation_date
69 - IS 'Timestamp when the entry was created';
70 -
71 -COMMENT ON COLUMN public.company_type.updated_date
72 - IS 'Timestamp for when the entry was last updated (set via application logic or triggers)';{{/code}}
73 -* (((
74 -== Company_relation ==
75 -
76 -*
77 -)))
31 + IS 'addresses table, instead of making use of addresses for ever company, customer and co... Prefer to make addresses table and then assign it to a company or a user etc.';