Ushbu eskizni yozishga maqola turtki bo'ldi . Menga 4 yil oldin chop etilgan maqola ham qiziq edi - .
Xuddi shu fikr qiziq tuyuldi - "ma'lumotlar bazasida biznes mantiqini amalga oshirish".
Yodga kelgan faqat men emas edi.
Shuningdek, kelajak uchun men, birinchi navbatda, amalga oshirish jarayonida yuzaga kelgan qiziqarli voqealarni o'zim uchun saqlab qolmoqchi edim. Ayniqsa, nisbatan yaqinda arxitekturani o'zgartirish va biznes mantig'ini backend darajasiga o'tkazish bo'yicha strategik qaror qabul qilinganligini hisobga olsak. Shunday qilib, ishlab chiqilgan hamma narsa tez orada hech kimga foyda keltirmaydi va hech kimni qiziqtirmaydi.
Ta'riflangan usullar qandaydir kashfiyot yoki istisno emas. Qanday qilib bilasiz, hamma narsa klassik va bir necha marta amalga oshirilgan (masalan, men 20 yil oldin Oracle'da shunga o'xshash yondashuvni qo'llaganman) Men hamma narsani bir joyda yig'ishga qaror qildim. Agar kimdir uchun foydali bo'lsa. Amaliyot shuni ko'rsatadiki, ko'pincha bir xil fikr turli odamlarga mustaqil ravishda keladi. Va uni o'zingiz uchun esdalik sifatida saqlash foydalidir.
Albatta, bu dunyoda hech narsa mukammal emas, xatolar va matn terish xatolari afsuski mumkin. Tanqid va mulohazalar mamnuniyat bilan qabul qilinadi va kutiladi va yana bir kichik tafsilot - amalga oshirishning o'ziga xos tafsilotlari e'tiborga olinmaydi. Shunga qaramay, hamma narsa hali ham haqiqiy ishchi loyihada qo'llaniladi. Shunday qilib, maqola shunchaki eskiz va umumiy tushunchaning tavsifi, boshqa hech narsa emas. Umid qilamanki, umumiy rasmni tushunish uchun etarli tafsilotlar mavjud.
Umumiy g'oya "bo'lin va mag'lub et, yashir va egalik qil".
G'oya klassik - jadvallar uchun alohida sxema, saqlangan funktsiyalar uchun alohida sxema.
Mijoz to'g'ridan-to'g'ri ma'lumotlarga kirish huquqiga ega emas. Mijoz qila oladigan yagona narsa - saqlangan funktsiyani chaqirish va olingan javobni qayta ishlash.
Rollar
CREATE ROLE store;
CREATE ROLE sys_functions;
CREATE ROLE loc_audit_functions;
CREATE ROLE service_functions;
CREATE ROLE business_functions;
Sxemalar
Jadvalni saqlash sxemasi
Mavzu ob'ektlarini amalga oshiradigan maqsadli jadvallar.
CREATE SCHEMA store AUTHORIZATION store ;
Tizim funktsiyalari diagrammasi
Tizim funktsiyalari, xususan, jadval o'zgarishlarini qayd qilish uchun.
CREATE SCHEMA sys_functions AUTHORIZATION sys_functions ;
Mahalliy audit sxemasi
Saqlangan funktsiyalarning bajarilishini mahalliy tekshirish va maqsadli jadvallarga o'zgartirishlar kiritish uchun funktsiyalar va jadvallar.
CREATE SCHEMA loc_audit_functions AUTHORIZATION loc_audit_functions;
Xizmat funktsiyasi diagrammasi
Xizmat va DML funktsiyalari uchun funktsiyalar.
CREATE SCHEMA service_functions AUTHORIZATION service_functions;
Biznes funktsiyalari diagrammasi
Mijoz tomonidan chaqirilgan yakuniy biznes funktsiyalari uchun funktsiyalar.
CREATE SCHEMA business_functions AUTHORIZATION business_functions;
ruxsatlar
Rol - DBA barcha sxemalarga to'liq kirish huquqiga ega (DB Egasi rolidan ajratilgan).
CREATE ROLE dba_role;
GRANT store TO dba_role;
GRANT sys_functions TO dba_role;
GRANT loc_audit_functions TO dba_role;
GRANT service_functions TO dba_role;
GRANT business_functions TO dba_role;
Rol - FOYDALANuvchi imtiyozga ega BOSHLASH diagrammada biznes_funktsiyalari.
CREATE ROLE user_role;
Sxemalar orasidagi imtiyozlar
Grant
Chunki barcha funksiyalar atribut bilan yaratilgan XAVFSIZLIK TAβNIYOR zarur ko'rsatmalar BARCHA FUNKSIYALARNI BAJARISHNI REKOR QILISh... Ommaga ochiq;
REVOKE EXECUTE ON ALL FUNCTION IN SCHEMA sys_functions FROM public ;
REVOKE EXECUTE ON ALL FUNCTION IN SCHEMA loc_audit_functions FROM public ;
REVOKE EXECUTE ON ALL FUNCTION IN SCHEMA service_functions FROM public ;
REVOKE EXECUTE ON ALL FUNCTION IN SCHEMA business_functions FROM public ;
GRANT USAGE ON SCHEMA sys_functions TO dba_role ;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA sys_functions TO dba_role ;
GRANT USAGE ON SCHEMA loc_audit_functions TO dba_role ;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA loc_audit_functions TO dba_role ;
GRANT USAGE ON SCHEMA service_functions TO dba_role ;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA service_functions TO dba_role ;
GRANT USAGE ON SCHEMA business_functions TO dba_role ;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA business_functions TO dba_role ;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA business_functions TO user_role ;
GRANT ALL PRIVILEGES ON SCHEMA store TO GROUP business_functions ;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA store TO business_functions ;
GRANT USAGE ON ALL SEQUENCES IN SCHEMA store TO business_functions ;
Shunday qilib, ma'lumotlar bazasi sxemasi tayyor. Siz ma'lumotlarni to'ldirishni boshlashingiz mumkin.
Maqsadli jadvallar
Jadvallarni yaratish juda oddiy. Hech qanday maxsus xususiyatlar yo'q, bundan tashqari, foydalanmaslikka qaror qilindi SERIAL va ketma-ketliklarni aniq hosil qiladi. Bundan tashqari, albatta, ko'rsatmalardan maksimal darajada foydalanish
COMMENT ON ...uchun sharhlar Π²ΡΠ΅Ρ ob'ektlar, istisnosiz.
Mahalliy audit
Saqlangan funktsiyalarning bajarilishini va maqsadli jadvallardagi o'zgarishlarni qayd qilish uchun mahalliy audit jadvali qo'llaniladi, u boshqa narsalar qatorida mijoz ulanishi tafsilotlarini, chaqirilgan modulning yorlig'ini, kiritilgan va haqiqiy qiymatlarni o'z ichiga oladi. JSON ko'rinishidagi chiqish parametrlari.
Tizim funktsiyalari
Maqsadli jadvallardagi o'zgarishlarni qayd qilish uchun mo'ljallangan. Ular trigger funktsiyalari.
Shablon - tizim funktsiyasi
---------------------------------------------------------
-- INSERT
CREATE OR REPLACE FUNCTION sys_functions.table_insert_log ()
RETURNS TRIGGER AS $$
BEGIN
PERFORM loc_audit_functions.make_log( ' '||'table' , 'insert' , json_build_object('id', NEW.id) );
RETURN NULL ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;
CREATE TRIGGER table_after_insert AFTER INSERT ON storage.table FOR EACH ROW EXECUTE PROCEDURE sys_functions.table_insert_log();
---------------------------------------------------------
-- UPDATE
CREATE OR REPLACE FUNCTION sys_functions.table_update_log ()
RETURNS TRIGGER AS $$
BEGIN
IF OLD.column != NEW.column
THEN
PERFORM loc_audit_functions.make_log( ' '||'table' , 'update' , json_build_object('OLD.column', OLD.column , 'NEW.column' , NEW.column ) );
END IF ;
RETURN NULL ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;
CREATE TRIGGER table_after_update AFTER UPDATE ON storage.table FOR EACH ROW EXECUTE PROCEDURE sys_functions.table_update_log ();
---------------------------------------------------------
-- DELETE
CREATE OR REPLACE FUNCTION sys_functions.table_delete_log ()
RETURNS TRIGGER AS $$
BEGIN
PERFORM loc_audit_functions.make_log( ' '||'table' , 'delete' , json_build_object('id', OLD.id ) );
RETURN NULL ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;
CREATE TRIGGER table_after_delete AFTER DELETE ON storage.table FOR EACH ROW EXECUTE PROCEDURE sys_functions.table_delete_log ();Xizmat funktsiyalari
Maqsadli jadvallarda xizmat ko'rsatish va DML operatsiyalarini amalga oshirish uchun mo'ljallangan.
Shablon - xizmat ko'rsatish funktsiyasi
--INSERT
--RETURN id OF NEW ROW
CREATE OR REPLACE FUNCTION service_functions.table_insert ( new_column store.table.column%TYPE )
RETURNS integer AS $$
DECLARE
new_id integer ;
BEGIN
-- Generate new id
new_id = nextval('store.table.seq');
-- Insert into table
INSERT INTO store.table
(
id ,
column
)
VALUES
(
new_id ,
new_column
);
RETURN new_id ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;
--DELETE
--RETURN ROW NUMBERS DELETED
CREATE OR REPLACE FUNCTION service_functions.table_delete ( current_id integer )
RETURNS integer AS $$
DECLARE
rows_count integer ;
BEGIN
DELETE FROM store.table WHERE id = current_id;
GET DIAGNOSTICS rows_count = ROW_COUNT;
RETURN rows_count ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;
-- UPDATE DETAILS
-- RETURN ROW NUMBERS UPDATED
CREATE OR REPLACE FUNCTION service_functions.table_update_column
(
current_id integer
,new_column store.table.column%TYPE
)
RETURNS integer AS $$
DECLARE
rows_count integer ;
BEGIN
UPDATE store.table
SET
column = new_column
WHERE id = current_id;
GET DIAGNOSTICS rows_count = ROW_COUNT;
RETURN rows_count ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;Biznes funktsiyalari
Mijoz tomonidan chaqirilgan yakuniy biznes funktsiyalari uchun mo'ljallangan. Ular har doim qaytib kelishadi - JSON. Amalga oshirish xatolarini to'xtatish va jurnalga kiritish uchun blokdan foydalaning Istisno.
Shablon - biznes funktsiyasi
CREATE OR REPLACE FUNCTION business_functions.business_function_template(
--Input parameters
)
RETURNS JSON AS $$
DECLARE
------------------------
--for exception catching
error_message text ;
error_json json ;
result json ;
------------------------
BEGIN
--LOGGING
PERFORM loc_audit_functions.make_log
(
'business_function_template',
'STARTED',
json_build_object
(
--IN Parameters
)
);
PERFORM business_functions.notice('business_function_template');
--START BUSINESS PART
--END BUSINESS PART
-- SUCCESFULLY RESULT
PERFORM business_functions.notice('result');
PERFORM business_functions.notice(result);
PERFORM loc_audit_functions.make_log
(
'business_function_template',
'FINISHED',
json_build_object( 'result',result )
);
RETURN result ;
----------------------------------------------------------------------------------------------------------
-- EXCEPTION CATCHING
EXCEPTION
WHEN OTHERS THEN
PERFORM loc_audit_functions.make_log
(
'business_function_template',
'STARTED',
json_build_object
(
--IN Parameters
) , TRUE );
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR',
json_build_object('SQLSTATE',SQLSTATE ), TRUE
);
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR',
json_build_object('SQLERRM',SQLERRM ), TRUE
);
GET STACKED DIAGNOSTICS error_message = RETURNED_SQLSTATE ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-RETURNED_SQLSTATE',json_build_object('RETURNED_SQLSTATE',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = COLUMN_NAME ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-COLUMN_NAME',
json_build_object('COLUMN_NAME',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = CONSTRAINT_NAME ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-CONSTRAINT_NAME',
json_build_object('CONSTRAINT_NAME',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = PG_DATATYPE_NAME ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-PG_DATATYPE_NAME',
json_build_object('PG_DATATYPE_NAME',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = MESSAGE_TEXT ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-MESSAGE_TEXT',json_build_object('MESSAGE_TEXT',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = SCHEMA_NAME ;
PERFORM loc_audit_functions.make_log
(s
'business_function_template',
' ERROR-SCHEMA_NAME',json_build_object('SCHEMA_NAME',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = PG_EXCEPTION_DETAIL ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-PG_EXCEPTION_DETAIL',
json_build_object('PG_EXCEPTION_DETAIL',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = PG_EXCEPTION_HINT ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-PG_EXCEPTION_HINT',json_build_object('PG_EXCEPTION_HINT',error_message ), TRUE );
GET STACKED DIAGNOSTICS error_message = PG_EXCEPTION_CONTEXT ;
PERFORM loc_audit_functions.make_log
(
'business_function_template',
' ERROR-PG_EXCEPTION_CONTEXT',json_build_object('PG_EXCEPTION_CONTEXT',error_message ), TRUE );
RAISE WARNING 'ALARM: %' , SQLERRM ;
SELECT json_build_object
(
'isError' , TRUE ,
'errorMsg' , SQLERRM
) INTO error_json ;
RETURN error_json ;
END
$$ LANGUAGE plpgsql SECURITY DEFINER;Xulosa
Umumiy rasmni tasvirlash uchun, menimcha, bu etarli. Agar kimdir tafsilotlar va natijalar bilan qiziqsa, sharhlar yozing, men rasmga qo'shimcha teginishlarni qo'shishdan xursand bo'laman.
PS
Ro'yxatga olish oddiy xato - parametr turini kiritish
-[ RECORD 1 ]-
date_trunc | 2020-08-19 13:15:46
id | 1072
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | STARTED
jsonb_pretty | {
| "dko": {
| "id": 4,
| "type": "Type1",
| "title": "CREATED BY addKD",
| "Weight": 10,
| "Tr": "300",
| "reduction": 10,
| "isTrud": "TRUE",
| "description": "decription",
| "lowerTr": "100",
| "measurement": "measurement1",
| "methodology": "m1",
| "passportUrl": "files",
| "upperTr": "200",
| "weightingFactor": 100.123,
| "actualTrValue": null,
| "upperTrCalcNumber": "120"
| },
| "CardId": 3
| }
-[ RECORD 2 ]-
date_trunc | 2020-08-19 13:15:46
id | 1073
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR
jsonb_pretty | {
| "SQLSTATE": "22P02"
| }
-[ RECORD 3 ]-
date_trunc | 2020-08-19 13:15:46
id | 1074
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR
jsonb_pretty | {
| "SQLERRM": "invalid input syntax for type numeric: "null""
| }
-[ RECORD 4 ]-
date_trunc | 2020-08-19 13:15:46
id | 1075
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-RETURNED_SQLSTATE
jsonb_pretty | {
| "RETURNED_SQLSTATE": "22P02"
| }
-[ RECORD 5 ]-
date_trunc | 2020-08-19 13:15:46
id | 1076
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-COLUMN_NAME
jsonb_pretty | {
| "COLUMN_NAME": ""
| }
-[ RECORD 6 ]-
date_trunc | 2020-08-19 13:15:46
id | 1077
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-CONSTRAINT_NAME
jsonb_pretty | {
| "CONSTRAINT_NAME": ""
| }
-[ RECORD 7 ]-
date_trunc | 2020-08-19 13:15:46
id | 1078
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-PG_DATATYPE_NAME
jsonb_pretty | {
| "PG_DATATYPE_NAME": ""
| }
-[ RECORD 8 ]-
date_trunc | 2020-08-19 13:15:46
id | 1079
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-MESSAGE_TEXT
jsonb_pretty | {
| "MESSAGE_TEXT": "invalid input syntax for type numeric: "null""
| }
-[ RECORD 9 ]-
date_trunc | 2020-08-19 13:15:46
id | 1080
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-SCHEMA_NAME
jsonb_pretty | {
| "SCHEMA_NAME": ""
| }
-[ RECORD 10 ]-
date_trunc | 2020-08-19 13:15:46
id | 1081
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-PG_EXCEPTION_DETAIL
jsonb_pretty | {
| "PG_EXCEPTION_DETAIL": ""
| }
-[ RECORD 11 ]-
date_trunc | 2020-08-19 13:15:46
id | 1082
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-PG_EXCEPTION_HINT
jsonb_pretty | {
| "PG_EXCEPTION_HINT": ""
| }
-[ RECORD 12 ]-
date_trunc | 2020-08-19 13:15:46
id | 1083
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-PG_EXCEPTION_CONTEXT
jsonb_pretty | {
usename | emp1
log_module | addKD
log_module_hash | 0b4c1529a89af3ddf6af3821dc790e8a
status | ERROR-MESSAGE_TEXT
jsonb_pretty | {
| "MESSAGE_TEXT": "invalid input syntax for type numeric: "null""
| }
Manba: www.habr.com