{"id":31385,"date":"2019-10-31T21:40:58","date_gmt":"2019-10-31T18:40:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper\/"},"modified":"2019-10-31T21:40:58","modified_gmt":"2019-10-31T18:40:58","slug":"biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper","title":{"rendered":"Obchodn\u00e1 logika v datab\u00e1ze pomocou SchemaKeeper","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Cie\u013eom tohto \u010dl\u00e1nku je na pr\u00edklade kni\u017enice schema-keeper<\/a><\/noindex> uk\u00e1za\u0165 n\u00e1stroje, ktor\u00e9 umo\u017e\u0148uj\u00fa podstatne zjednodu\u0161i\u0165 proces v\u00fdvoja datab\u00e1z v r\u00e1mci PHP projektov pou\u017e\u00edvaj\u00facich datab\u00e1zu PostgreSQL.<\/p>\n

<\/p>\n

Inform\u00e1cie z tohto \u010dl\u00e1nku bud\u00fa predov\u0161etk\u00fdm u\u017eito\u010dn\u00e9 pre v\u00fdvoj\u00e1rov, ktor\u00ed chc\u00fa maxim\u00e1lne vyu\u017ei\u0165 mo\u017enosti PostgreSQL, ale stret\u00e1vaj\u00fa sa s probl\u00e9mami spr\u00e1vy obchodnej logiky, presunutej do DB. <\/p>\n

<\/p>\n

\u010cl\u00e1nok nebude popisova\u0165 v\u00fdhody alebo nev\u00fdhody uchov\u00e1vania obchodnej logiky v datab\u00e1ze. Predpoklad\u00e1 sa, \u017ee \u010ditate\u013e si u\u017e v\u00fdber urobil.<\/p>\n

<\/p>\n

Bude sa zaobera\u0165 nasleduj\u00facimi ot\u00e1zkami:<\/p>\n

<\/p>\n

    \n
  1. V akom form\u00e1te uchov\u00e1va\u0165 dump \u0161trukt\u00fary DB v syst\u00e9me na kontrolu verzi\u00ed (\u010falej len VCS)<\/li>\n
  2. Ako sledova\u0165 zmeny v \u0161trukt\u00fare DB po ulo\u017een\u00ed dumpu<\/li>\n
  3. Ako pren\u00e1\u0161a\u0165 zmeny v \u0161trukt\u00fare DB do in\u00fdch prostred\u00ed bez konfliktov a obrovsk\u00fdch s\u00faborov migr\u00e1ci\u00ed<\/li>\n
  4. Ako nastavi\u0165 proces paralelnej pr\u00e1ce na projekte viacer\u00fdch v\u00fdvoj\u00e1rov<\/li>\n
  5. Ako bezpe\u010dne nasadzova\u0165 v\u00e4\u010d\u0161ie mno\u017estvo zmien v \u0161trukt\u00fare DB na produk\u010dn\u00e9 prostredie<\/a><\/noindex>
    \n

    SchemaKeeper<\/strong> je optimalizovan\u00fd na pr\u00e1cu s ulo\u017een\u00fdmi proced\u00farami nap\u00edsan\u00fdmi v jazyku PL\/pgSQL<\/a><\/noindex>. Testovanie s in\u00fdmi jazykmi nebolo vykonan\u00e9, preto m\u00f4\u017ee by\u0165 pou\u017eitie menej efekt\u00edvne alebo nemo\u017en\u00e9.\n<\/p><\/blockquote>\n<\/li>\n<\/ol>\n

    <\/p>\n

    V akom form\u00e1te uchov\u00e1va\u0165 dump \u0161trukt\u00fary DB v VCS<\/h2>\n

    <\/p>\n

    Kni\u017enica schema-keeper<\/a><\/noindex> poskytuje funkciu saveDump<\/code>, ktor\u00e1 uchov\u00e1va \u0161trukt\u00faru v\u0161etk\u00fdch objektov z DB vo forme samostatn\u00fdch textov\u00fdch s\u00faborov. Na v\u00fdstupe sa vytvor\u00ed adres\u00e1r obsahuj\u00faci \u0161trukt\u00faru DB rozdelen\u00fa na skupinov\u00e9 s\u00fabory, ktor\u00e9 je mo\u017en\u00e9 \u013eahko prida\u0165 do VCS.<\/p>\n

    <\/p>\n

    Pozrime sa na transform\u00e1ciu objektov z DB do s\u00faborov na nieko\u013ek\u00fdch pr\u00edkladoch:<\/p>\n

    <\/p>\n

    Typ objektu
    \nSch\u00e9ma
    \nN\u00e1zov
    \nRelat\u00edvna cesta k s\u00faboru<\/p>\n

    Tabu\u013eka
    \npublic
    \naccounts
    \n.\/public\/tables\/accounts.txt<\/code><\/p>\n

    Ulo\u017een\u00e1 proced\u00fara
    \npublic
    \nauth(hash bigint)
    \n.\/public\/functions\/auth(int8).sql<\/code><\/p>\n

    Poh\u013ead
    \nbooking
    \ntariffs
    \n.\/booking\/views\/tariffs.txt<\/code><\/p>\n

    <\/p>\n

    Obsah s\u00faborov je textov\u00fa reprezent\u00e1ciu \u0161trukt\u00fary konkr\u00e9tneho objektu DB. Napr\u00edklad pre ulo\u017een\u00e9 proced\u00fary bude obsah s\u00faboru kompletn\u00e9 ur\u010denie ulo\u017een\u00e9 proced\u00fary za\u010d\u00ednaj\u00face blokom CREATE OR REPLACE FUNCTION<\/code>.<\/p>\n

    <\/p>\n

    Ako je vidie\u0165 z tabu\u013eky vy\u0161\u0161ie, cesta k s\u00faboru obsahuje inform\u00e1cie o type, sch\u00e9me a n\u00e1zve objektu. Tak\u00fdto pr\u00edstup u\u013eah\u010duje navig\u00e1ciu v dumpe a k\u00f3dov\u00fa kontrolu zmien v DB.<\/p>\n

    <\/p>\n

    Pr\u00edpona .sql<\/code> pre s\u00fabory s k\u00f3dom ulo\u017een\u00fdch proced\u00far je vybran\u00e9, aby IDE automaticky poskytovalo n\u00e1stroje na interakciu s DB pri otvoren\u00ed s\u00faboru.<\/p><\/blockquote>\n

    <\/p>\n

    Ako sledova\u0165 zmeny v \u0161trukt\u00fare DB po ulo\u017een\u00ed dumpu<\/h2>\n

    <\/p>\n

    Ulo\u017een\u00edm dumpu aktu\u00e1lnej \u0161trukt\u00fary DB do VCS z\u00edskavame mo\u017enos\u0165 overi\u0165, \u010di boli vykonan\u00e9 zmeny v \u0161trukt\u00fare datab\u00e1zy po vytvoren\u00ed dumpu. V kni\u017enici schema-keeper<\/a><\/noindex> na zistenie zmien \u0161trukt\u00fary DB je predpokladan\u00e1 funkcia verifyDump<\/code>, ktor\u00e1 bez ved\u013eaj\u0161\u00edch \u00fa\u010dinkov vracia inform\u00e1cie o rozdieloch. <\/p>\n

    <\/p>\n

    Alternat\u00edvny sp\u00f4sob overenia \u2014 znovu zavola\u0165 funkciu saveDump<\/code>, zadaj\u00fac t\u00fa ist\u00fa adres\u00e1ru a overi\u0165 v VCS pr\u00edtomnos\u0165 zmien. Ke\u010f\u017ee v\u0161etky objekty z DB s\u00fa ulo\u017een\u00e9 v samostatn\u00fdch s\u00faboroch, VCS uk\u00e1\u017ee iba zmenen\u00e9 objekty.
    \nHlavn\u00e1 nev\u00fdhoda tohto sp\u00f4sobu \u2014 potreba prepisovania s\u00faborov, aby sme videli zmeny.<\/p>\n

    <\/p>\n

    Ako pren\u00e1\u0161a\u0165 zmeny v \u0161trukt\u00fare DB do in\u00fdch prostred\u00ed bez konfliktov a obrovsk\u00fdch s\u00faborov migr\u00e1ci\u00ed<\/h2>\n

    <\/p>\n

    V\u010faka funkcii deployDump<\/code> m\u00f4\u017ee by\u0165 zdrojov\u00fd k\u00f3d ulo\u017een\u00fdch proced\u00far upravovan\u00fd \u00faplne rovnako ako be\u017en\u00fd zdrojov\u00fd k\u00f3d aplik\u00e1cie. M\u00f4\u017eete prid\u00e1va\u0165\/odstra\u0148ova\u0165 nov\u00e9 riadky v k\u00f3de ulo\u017een\u00fdch proced\u00far a okam\u017eite posiela\u0165 zmeny do syst\u00e9mu spr\u00e1vy verzi\u00ed alebo vytv\u00e1ra\u0165\/odstra\u0148ova\u0165 ulo\u017een\u00e9 proced\u00fary vytvoren\u00edm\/odstr\u00e1nen\u00edm pr\u00edslu\u0161n\u00fdch s\u00faborov v adres\u00e1ri s dumpom. <\/p>\n

    <\/p>\n

    Napr\u00edklad na vytvorenie novej ulo\u017een\u00e9 proced\u00fary v sch\u00e9me public<\/code> sta\u010d\u00ed vytvori\u0165 nov\u00fd s\u00fabor s pr\u00edponou .sql<\/code> v adres\u00e1ri public\/functions<\/code>, vlo\u017ei\u0165 do neho zdrojov\u00fd k\u00f3d ulo\u017een\u00e9 proced\u00fary, vr\u00e1tane bloku CREATE OR REPLACE FUNCTION<\/code>, potom zavola\u0165 funkciu deployDump<\/code>. Podobne sa deje aj zmena a odstr\u00e1nenie ulo\u017een\u00e9 proced\u00fary. Takto sa k\u00f3d z\u00e1rove\u0148 dost\u00e1va aj do VCS, aj do datab\u00e1zy. <\/p>\n

    <\/p>\n

    Ak sa v zdrojovom k\u00f3de nejakej ulo\u017een\u00e9 proced\u00fary objav\u00ed chyba alebo nezrovnalos\u0165 medzi n\u00e1zvami s\u00faboru a ulo\u017een\u00e9 proced\u00farou, potom deployDump<\/code> sa nevykon\u00e1 a zobraz\u00ed text chyby. Nes\u00falad ulo\u017een\u00fdch proced\u00far medzi dumpom a aktu\u00e1lnou DB je nemo\u017en\u00fd pri pou\u017eit\u00ed deployDump<\/code>.<\/p>\n

    <\/p>\n

    Pri vytv\u00e1ran\u00ed novej ulo\u017een\u00e9 proced\u00fary nie je potrebn\u00e9 ru\u010dne zad\u00e1va\u0165 spr\u00e1vny n\u00e1zov s\u00faboru. Sta\u010d\u00ed, aby mal s\u00fabor pr\u00edponu .sql<\/code>. Po zavolan\u00ed deployDump<\/code> text chyby bude obsahova\u0165 spr\u00e1vny n\u00e1zov, ktor\u00fd mo\u017eno pou\u017ei\u0165 na premenovanie s\u00faboru.<\/p><\/blockquote>\n

    deployDump<\/code> umo\u017e\u0148uje meni\u0165 parametre funkcie alebo n\u00e1vratov\u00fd typ bez \u010fal\u0161\u00edch akci\u00ed, zatia\u013e \u010do pri klasickom pr\u00edstupe by bolo treba
    \nnajprv vykona\u0165 DROP FUNCTION<\/code>, a a\u017e potom CREATE OR REPLACE FUNCTION<\/code>.<\/p>\n

    <\/p>\n

    \u017dia\u013e, existuj\u00fa niektor\u00e9 situ\u00e1cie, kedy deployDump<\/code> nie je mo\u017en\u00e9 automaticky uplatni\u0165 zmeny. Napr\u00edklad ak sa odstr\u00e1ni sp\u00fa\u0161\u0165acia funkcia, ktor\u00e1 je pou\u017e\u00edvan\u00e1 aspo\u0148 jednou sp\u00fa\u0161\u0165ou. Tak\u00e9to situ\u00e1cie sa rie\u0161ia manu\u00e1lne pomocou migra\u010dn\u00fdch s\u00faborov.<\/p>\n

    <\/p>\n

    Ak za pren\u00e1\u0161anie zmien v ulo\u017een\u00fdch proced\u00farach zodpoved\u00e1 samotn\u00fd schema-keeper<\/a><\/noindex>, tak na pren\u00e1\u0161anie ostatn\u00fdch zmien v \u0161trukt\u00fare je potrebn\u00e9 pou\u017ei\u0165 migra\u010dn\u00e9 s\u00fabory. Napr\u00edklad dobr\u00e1 kni\u017enica na pr\u00e1cu s migr\u00e1ciami je doctrine\/migrations<\/a><\/noindex>.<\/p>\n

    <\/p>\n

    Migr\u00e1cie musia by\u0165 aplikovan\u00e9 pred spusten\u00edm deployDump<\/code>. To umo\u017e\u0148uje zavies\u0165 v\u0161etky zmeny v \u0161trukt\u00fare a rie\u0161i\u0165 problematick\u00e9 situ\u00e1cie, aby sa zmeny v ulo\u017een\u00fdch proced\u00farach nahrali bez probl\u00e9mov.<\/p>\n

    <\/p>\n

    Podrobnej\u0161ie sa pr\u00e1ca s migr\u00e1ciami pop\u00ed\u0161e v nasleduj\u00facich \u010dastiach.<\/p>\n

    <\/p>\n

    Ako nastavi\u0165 proces paralelnej pr\u00e1ce na projekte viacer\u00fdch v\u00fdvoj\u00e1rov<\/h2>\n

    <\/p>\n

    Je potrebn\u00e9 vytvori\u0165 skript na \u00fapln\u00fa inicializ\u00e1ciu DB, ktor\u00fd bude spusten\u00fd v\u00fdvoj\u00e1rom na jeho pracovnej stanici, \u010d\u00edm sa privedie \u0161trukt\u00fara lok\u00e1lnej DB do zhody s ulo\u017een\u00fdm v VCS dumpom. Najjednoduch\u0161ie je rozdeli\u0165 inicializ\u00e1ciu lok\u00e1lnej DB na 3 kroky:<\/p>\n

    <\/p>\n

      \n
    1. Import s\u00faboru s z\u00e1kladnou \u0161trukt\u00farou, ktor\u00fd bude nazvan\u00fd napr\u00edklad base.sql<\/code> <\/li>\n
    2. Aplik\u00e1cia migr\u00e1ci\u00ed<\/li>\n
    3. Vyvolanie deployDump<\/code><\/li>\n<\/ol>\n

      <\/p>\n

      base.sql<\/code> \u2014 to je v\u00fdchodiskov\u00fd bod, na ktor\u00fd sa aplikuj\u00fa migr\u00e1cie a vykon\u00e1va sa deployDump<\/code>, t.j. base.sql + migr\u00e1cie + deployDump = aktu\u00e1lna \u0161trukt\u00fara DB<\/code>. Tak\u00fdto s\u00fabor mo\u017eno vytvori\u0165 pomocou utilitky pg_dump<\/code>. Pou\u017e\u00edva sa base.sql<\/code> v\u00fdhradne pri inicializ\u00e1cii datab\u00e1zy z nuly.<\/p><\/blockquote>\n

      Nazvime skript na \u00fapln\u00fa inicializ\u00e1ciu DB refresh.sh<\/code>. Pracovn\u00fd proces m\u00f4\u017ee vyzera\u0165 nasledovne:<\/p>\n

      <\/p>\n

        \n
      1. V\u00fdvoj\u00e1r spust\u00ed vo svojom prostred\u00ed refresh.sh<\/code> a z\u00edska aktu\u00e1lnu \u0161trukt\u00faru DB<\/li>\n
      2. V\u00fdvoj\u00e1r za\u010dne pracova\u0165 na zadanom \u00falohe, modifikuj\u00fac lok\u00e1lnu DB na potreby nov\u00fdch funk\u010dnost\u00ed (ALTER TABLE ... ADD COLUMN<\/code> at\u010f.)<\/li>\n
      3. Po dokon\u010den\u00ed \u00falohy v\u00fdvoj\u00e1r vyvol\u00e1 funkciu saveDump<\/code>, aby ulo\u017eil do VCS zmeny vykonan\u00e9 v DB<\/li>\n
      4. V\u00fdvoj\u00e1r znovu sp\u00fa\u0161\u0165a refresh.sh<\/code>, potom verifyDump<\/code>, ktor\u00fd teraz zobrazuje zoznam zmien na zaradenie do migr\u00e1cie<\/li>\n
      5. V\u00fdvoj\u00e1r prenesie v\u0161etky zmeny \u0161trukt\u00fary do migra\u010dn\u00e9ho s\u00faboru, sp\u00fa\u0161\u0165a op\u00e4\u0165 refresh.sh<\/code> a verifyDump<\/code>, a ak je migr\u00e1cia spr\u00e1vne zostaven\u00e1, verifyDump<\/code> vyk\u00e1\u017ee absenciu rozdielov medzi lok\u00e1lnou DB a ulo\u017een\u00fdm dumpom<\/li>\n<\/ol>\n

        <\/p>\n

        Popisovan\u00fd proces je kompatibiln\u00fd s princ\u00edpmi gitflow. Ka\u017ed\u00e1 vetva vo VCS bude obsahova\u0165 svoju verziu dumpu, a pri zl\u00fa\u010den\u00ed vetiev d\u00f4jde k zl\u00fa\u010deniu dumpov. V drvivej v\u00e4\u010d\u0161ine pr\u00edpadov nie je potrebn\u00e9 vykon\u00e1va\u0165 \u017eiadne dodato\u010dn\u00e9 akcie, ale ak boli v r\u00f4znych vetv\u00e1ch vykonan\u00e9 zmeny, napr\u00edklad v tej istej tabu\u013eke, m\u00f4\u017ee d\u00f4js\u0165 ku konfliktu.<\/p>\n

        <\/p>\n

        Zv\u00e1\u017eme konfliktov\u00fa situ\u00e1ciu na pr\u00edklade: existuje vetva develop<\/em>, od ktorej s\u00fa odvetven\u00e9 dve vetvy: feature1<\/em> a feature2<\/em>, ktor\u00e9 nemaj\u00fa konflikty s develop<\/em>, ale maj\u00fa konflikty medzi sebou. Je potrebn\u00e9 vykona\u0165 zl\u00fa\u010denie oboch vetiev do develop<\/em>. Pre tak\u00fdto pr\u00edpad sa odpor\u00fa\u010da najprv vykona\u0165 zl\u00fa\u010denie jednej z vetiev do develop<\/em>, a potom zl\u00fa\u010denie develop<\/em> do zost\u00e1vaj\u00facej vetvy, pri\u010dom sa vyrie\u0161ia konflikty v zost\u00e1vaj\u00facej vetve, po ktor\u00fdch sa vykon\u00e1 zl\u00fa\u010denie poslednej vetvy do develop<\/em>. Po\u010das f\u00e1zy rie\u0161enia konfliktov m\u00f4\u017ee by\u0165 potrebn\u00e9 upravi\u0165 migra\u010dn\u00fd s\u00fabor v poslednej vetve, aby zodpovedal fin\u00e1lnemu dumpu, ktor\u00fd zahrnuje v\u00fdsledky zl\u00fa\u010den\u00ed.<\/p>\n

        <\/p>\n

        Ako bezpe\u010dne nasadzova\u0165 v\u00e4\u010d\u0161ie mno\u017estvo zmien v \u0161trukt\u00fare DB na produk\u010dn\u00e9 prostredie<\/h2>\n

        <\/p>\n

        V\u010faka pr\u00edtomnosti dumpu aktu\u00e1lnej \u0161trukt\u00fary datab\u00e1zy vo VCS je mo\u017en\u00e9 skontrolova\u0165 produk\u010dn\u00fa datab\u00e1zu na presn\u00fa zhodu s po\u017eadovanou \u0161trukt\u00farou. To zaru\u010duje, \u017ee do produk\u010dnej datab\u00e1zy sa \u00faspe\u0161ne preniesli v\u0161etky zmeny, ktor\u00e9 navrhli v\u00fdvoj\u00e1ri.<\/p>\n

        <\/p>\n

        Ke\u010f\u017ee DDL<\/a><\/noindex> v PostgreSQL je transak\u010dn\u00fd<\/a><\/noindex>, odpor\u00fa\u010da sa dodr\u017eiava\u0165 nasleduj\u00faci poriadok nasadenia, aby sa, v pr\u00edpade neo\u010dak\u00e1vanej chyby, \"bezbolestne\" vykonal ROLLBACK<\/code>:<\/p>\n

        <\/p>\n

          \n
        1. Za\u010da\u0165 transakciu<\/li>\n
        2. V transakcii vykona\u0165 v\u0161etky migr\u00e1cie<\/li>\n
        3. V tej istej transakcii vykona\u0165 deployDump<\/code><\/li>\n
        4. Bez ukon\u010denia transakcie vykona\u0165 verifyDump<\/code>. Ak nie s\u00fa \u017eiadne chyby, vykona\u0165 COMMIT<\/code>. Ak s\u00fa chyby, vykona\u0165 ROLLBACK<\/code><\/li>\n<\/ol>\n

          <\/p>\n

          Tieto kroky sa pomerne jednoducho integruj\u00fa do existuj\u00facich pr\u00edstupov k nasadeniu aplik\u00e1ci\u00ed, vr\u00e1tane zero-downtime.<\/p>\n

          <\/p>\n

          Z\u00e1ver<\/h1>\n

          <\/p>\n

          V\u010faka vy\u0161\u0161ie uveden\u00fdm met\u00f3dam je mo\u017en\u00e9 z projektov \"PHP + PostgreSQL\" vy\u0165a\u017ei\u0165 maxim\u00e1lnu v\u00fdkonnos\u0165, pri\u010dom sa obetuje relat\u00edvne mal\u00e9 mno\u017estvo pohodlia pri v\u00fdvoji v porovnan\u00ed s implement\u00e1ciou celej obchodnej logiky v hlavnom k\u00f3de aplik\u00e1cie. Navy\u0161e, spracovanie \u00fadajov v PL\/pgSQL<\/a><\/noindex> \u010dasto vyzer\u00e1 prieh\u013eadnej\u0161ie a vy\u017eaduje menej k\u00f3du ako rovnak\u00e1 funkcionalita nap\u00edsan\u00e1 v PHP.<\/p>\n

          Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

          \u0426\u0435\u043b\u044c \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u2014 \u043d\u0430 \u043f\u0440\u0438\u043c\u0435\u0440\u0435 \u0431\u0438\u0431\u043b\u0438\u043e\u0442\u0435\u043a\u0438 schema-keeper \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043e\u0431\u043b\u0435\u0433\u0447\u0438\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0431\u0430\u0437 \u0434\u0430\u043d\u043d\u044b\u0445 \u0432 \u0440\u0430\u043c\u043a\u0430\u0445 PHP-\u043f\u0440\u043e\u0435\u043a\u0442\u043e\u0432, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u0421\u0423\u0411\u0414 PostgreSQL. \u0418\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044f \u0438\u0437 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438, \u0432 \u043f\u0435\u0440\u0432\u0443\u044e \u043e\u0447\u0435\u0440\u0435\u0434\u044c, \u0431\u0443\u0434\u0435\u0442 \u043f\u043e\u043b\u0435\u0437\u043d\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0430\u043c, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e \u043c\u0430\u043a\u0441\u0438\u043c\u0443\u043c\u0443 \u0445\u043e\u0442\u044f\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 PostgreSQL, \u043d\u043e \u0441\u0442\u0430\u043b\u043a\u0438\u0432\u0430\u044e\u0442\u0441\u044f \u0441 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u043c\u0438 \u0441\u043e\u043f\u0440\u043e\u0432\u043e\u0436\u0434\u0435\u043d\u0438\u044f \u0431\u0438\u0437\u043d\u0435\u0441-\u043b\u043e\u0433\u0438\u043a\u0438, \u0432\u044b\u043d\u0435\u0441\u0435\u043d\u043d\u043e\u0439 \u0432 \u0411\u0414. \u0421\u0442\u0430\u0442\u044c\u044f \u043d\u0435 \u0431\u0443\u0434\u0435\u0442 \u043e\u043f\u0438\u0441\u044b\u0432\u0430\u0442\u044c \u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31385","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Obchodn\u00e1 logika v datab\u00e1ze pomocou SchemaKeeper | ProHoster","description":"Cie\u013eom tohto \u010dl\u00e1nku je na pr\u00edklade kni\u017enice schema-keeper uk\u00e1za\u0165 n\u00e1stroje, ktor\u00e9 umo\u017e\u0148uj\u00fa v\u00fdrazne.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0411\u0438\u0437\u043d\u0435\u0441-\u043b\u043e\u0433\u0438\u043a\u0430 \u0432 \u0431\u0430\u0437\u0435 \u0434\u0430\u043d\u043d\u044b\u0445 \u043f\u0440\u0438 \u043f\u043e\u043c\u043e\u0449\u0438 SchemaKeeper | ProHoster","og:description":"\u0426\u0435\u043b\u044c \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u2014 \u043d\u0430 \u043f\u0440\u0438\u043c\u0435\u0440\u0435 \u0431\u0438\u0431\u043b\u0438\u043e\u0442\u0435\u043a\u0438 schema-keeper \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:40:58+00:00","article:modified_time":"2019-10-31T18:40:58+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31385","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 05:54:24","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:17:26","updated":"2026-01-21 05:54:24","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=31385"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31385\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=31385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=31385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=31385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}