{"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\/sq\/blog\/administrirovanie\/biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper","title":{"rendered":"Logjika e biznesit n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave me ndihm\u00ebn e SchemaKeeper","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Q\u00ebllimi i k\u00ebtij artikulli \u00ebsht\u00eb t\u00eb ilustroj\u00eb me shembuj nga biblioteka schema-keeper<\/a><\/noindex> mjetet q\u00eb lejojn\u00eb t\u00eb ndihmojn\u00eb ndjesh\u00ebm procesin e zhvillimit t\u00eb bazave t\u00eb dh\u00ebnash n\u00eb projektet PHP q\u00eb p\u00ebrdorin DBMS PostgreSQL.<\/p>\n

<\/p>\n

Informacioni n\u00eb k\u00ebt\u00eb artikull do t\u00eb jet\u00eb sidomos i dobish\u00ebm p\u00ebr zhvilluesit q\u00eb duan t\u00eb shfryt\u00ebzojn\u00eb n\u00eb maksimum mund\u00ebsit\u00eb e PostgreSQL, por p\u00ebrballen me probleme n\u00eb mb\u00ebshtetje t\u00eb logjik\u00ebs s\u00eb biznesit t\u00eb p\u00ebrfshir\u00eb n\u00eb DB. <\/p>\n

<\/p>\n

Artikulli nuk do t\u00eb p\u00ebrshkruaj\u00eb p\u00ebrpar\u00ebsit\u00eb ose disavantazhet e ruajtjes s\u00eb logjik\u00ebs s\u00eb biznesit n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave. Pranohet q\u00eb zgjedhja tashm\u00eb \u00ebsht\u00eb b\u00ebr\u00eb nga lexuesi.<\/p>\n

<\/p>\n

Do t\u00eb shqyrtohen \u00e7\u00ebshtjet e m\u00ebposhtme:<\/p>\n

<\/p>\n

    \n
  1. Si t\u00eb ruhet dumpi i struktur\u00ebs s\u00eb DB n\u00eb sistemin e kontrollit t\u00eb versioneve (VCS)<\/li>\n
  2. Si t\u00eb gjurmohen ndryshimet n\u00eb struktur\u00ebn e DB pas ruajtjes s\u00eb dumpit<\/li>\n
  3. Si t\u00eb transferohen ndryshimet n\u00eb struktur\u00ebn e DB n\u00eb mjedise t\u00eb tjera pa konflikte dhe skedar\u00eb migrimi gjigant\u00eb<\/li>\n
  4. Si t\u00eb organizohet procesi i pun\u00ebs paralele t\u00eb disa zhvilluesve n\u00eb projekt<\/li>\n
  5. Si t\u00eb depozitohen n\u00eb m\u00ebnyr\u00eb t\u00eb sigurt\u00eb nj\u00eb num\u00ebr t\u00eb madh t\u00eb ndryshimeve n\u00eb struktur\u00ebn e DB n\u00eb mjedisin production<\/a><\/noindex>
    \n

    SchemaKeeper<\/strong> \u00ebsht\u00eb krijuar p\u00ebr t\u00eb punuar me procedurat e ruajtura t\u00eb shkruara n\u00eb gjuh\u00ebn PL\/pgSQL<\/a><\/noindex>. Testimi me gjuh\u00eb t\u00eb tjera nuk \u00ebsht\u00eb kryer, k\u00ebshtu q\u00eb p\u00ebrdorimi mund t\u00eb mos jet\u00eb aq efikas, ose i pamundur.\n<\/p><\/blockquote>\n<\/li>\n<\/ol>\n

    <\/p>\n

    Si t\u00eb ruhet dumpi i struktur\u00ebs s\u00eb DB n\u00eb VCS<\/h2>\n

    <\/p>\n

    Biblioteka schema-keeper<\/a><\/noindex> ofron funksionin saveDump<\/code>, i cili ruan struktur\u00ebn e t\u00eb gjith\u00eb objekteve nga DB si skedar\u00eb t\u00eb ve\u00e7ant\u00eb tekstual\u00eb. N\u00eb fund krijohet nj\u00eb direktori q\u00eb p\u00ebrmban struktur\u00ebn e DB, e cila \u00ebsht\u00eb e ndar\u00eb n\u00eb skedar\u00eb t\u00eb grupuar q\u00eb mund t\u00eb shtohen leht\u00ebsisht n\u00eb VCS.<\/p>\n

    <\/p>\n

    Le t\u00eb shqyrtojm\u00eb transformimin e objekteve nga DB n\u00eb skedar\u00eb n\u00eb disa shembuj:<\/p>\n

    <\/p>\n

    Tipi i objektit
    \nSkema
    \nEmri
    \nRruga relative deri n\u00eb skedar<\/p>\n

    Tabela
    \npublike
    \naccounts
    \n.\/public\/tables\/accounts.txt<\/code><\/p>\n

    Procedura e ruajtur
    \npublike
    \nauth(hash bigint)
    \n.\/public\/functions\/auth(int8).sql<\/code><\/p>\n

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

    <\/p>\n

    P\u00ebrmbajtja e skedar\u00ebve \u00ebsht\u00eb nj\u00eb p\u00ebrfaq\u00ebsim tekstual i struktur\u00ebs s\u00eb objektit specifik DB. P\u00ebr shembull, p\u00ebr procedurat e ruajtura, p\u00ebrmbajtja e skedarit do t\u00eb jet\u00eb definimi i plot\u00eb i procedur\u00ebs s\u00eb ruajtur, duke filluar nga blloku CREATE OR REPLACE FUNCTION<\/code>.<\/p>\n

    <\/p>\n

    Si\u00e7 duket nga tabela m\u00eb sip\u00ebr, rruga e skedarit p\u00ebrmban informacion mbi tipin, skem\u00ebn dhe emrin e objektit. Ky qasje leht\u00ebson navigimin n\u00eb dump dhe rishikimin e ndryshimeve n\u00eb DB.<\/p>\n

    <\/p>\n

    Zgjerimi .sql<\/code> p\u00ebr skedar\u00ebt me kodin burimor t\u00eb procedurave t\u00eb ruajtura u zgjodh p\u00ebr t\u00eb mund\u00ebsuar q\u00eb IDE t\u00eb ofronin automatikisht mjete p\u00ebr nd\u00ebrveprimin me DB kur hapet skedari.<\/p><\/blockquote>\n

    <\/p>\n

    Si t\u00eb gjurmohen ndryshimet n\u00eb struktur\u00ebn e DB pas ruajtjes s\u00eb dumpit<\/h2>\n

    <\/p>\n

    Duke ruajtur dumpin e struktur\u00ebs aktuale t\u00eb DB n\u00eb VCS, ne krijojm\u00eb mund\u00ebsin\u00eb p\u00ebr t\u00eb verifikuar n\u00ebse jan\u00eb b\u00ebr\u00eb ndryshime n\u00eb struktur\u00ebn e baz\u00ebs pas krijimit t\u00eb dumpit. N\u00eb bibliotek\u00eb schema-keeper<\/a><\/noindex> p\u00ebr identifikimin e ndryshimeve n\u00eb struktur\u00ebn e DB \u00ebsht\u00eb parashikuar funksioni verifyDump<\/code>, i cili pa efekte an\u00ebsore kthen informacion mbi ndryshimet. <\/p>\n

    <\/p>\n

    Nj\u00eb m\u00ebnyr\u00eb alternative p\u00ebr kontrollin \u2014 t\u00eb th\u00ebrras\u00ebsh p\u00ebrs\u00ebri funksionin saveDump<\/code>, duke caktuar t\u00eb nj\u00ebjt\u00ebn direktori dhe t\u00eb kontrollosh n\u00eb VCS pranin\u00eb e ndryshimeve. Duke qen\u00eb se t\u00eb gjith\u00eb objektet nga DB jan\u00eb ruajtur n\u00eb skedar\u00eb t\u00eb ve\u00e7ant\u00eb, VCS do t\u00eb tregoj\u00eb vet\u00ebm objektet e ndryshuara.
    \nPika kryesore negative e k\u00ebtij m\u00ebnyre \u00ebsht\u00eb nevoja p\u00ebr t\u00eb rishkruar skedar\u00ebt p\u00ebr t\u00eb par\u00eb ndryshimet.<\/p>\n

    <\/p>\n

    Si t\u00eb transferohen ndryshimet n\u00eb struktur\u00ebn e DB n\u00eb mjedise t\u00eb tjera pa konflikte dhe skedar\u00eb migrimi gjigant\u00eb<\/h2>\n

    <\/p>\n

    Fal\u00eb funksionit deployDump<\/code> kodin burimor t\u00eb procedurave t\u00eb ruajtura mund t\u00eb modifikohet n\u00eb m\u00ebnyr\u00eb krejt\u00ebsisht t\u00eb ngjashme me kodin burimor t\u00eb aplikacionit. Mund t\u00eb shtoni\/fshini linja t\u00eb reja n\u00eb kodin e procedurave t\u00eb ruajtura dhe menj\u00ebher\u00eb t\u00eb d\u00ebrgoni ndryshimet n\u00eb sistemin e kontrollit t\u00eb versioneve, ose t\u00eb krijoni\/fshini procedura t\u00eb ruajtura duke krijuar\/fshir\u00eb skedar\u00ebt p\u00ebrkat\u00ebs n\u00eb direktorin\u00eb e dumpit. <\/p>\n

    <\/p>\n

    P\u00ebr shembull, p\u00ebr t\u00eb krijuar nj\u00eb procedur\u00eb t\u00eb re t\u00eb ruajtur n\u00eb skem\u00ebn publike<\/code> mjafton t\u00eb krijosh nj\u00eb skedar t\u00eb ri me zgjerim .sql<\/code> n\u00eb direktorin\u00eb public\/functions<\/code>, t\u00eb vendos\u00ebsh n\u00eb t\u00eb kodin burimor t\u00eb procedur\u00ebs s\u00eb ruajtur, duke p\u00ebrfshir\u00eb bllokun CREATE OR REPLACE FUNCTION<\/code>, pastaj t\u00eb th\u00ebrras\u00ebsh funksionin deployDump<\/code>. Po ashtu ndodhin ndryshimet dhe fshirjet e procedurave t\u00eb ruajtura. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, kodi i nj\u00ebher\u00ebsh depersonalizohet n\u00eb VCS, po ashtu dhe n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave. <\/p>\n

    <\/p>\n

    N\u00ebse n\u00eb kodin burimor t\u00eb ndonj\u00eb procedure t\u00eb ruajtur shfaqet nj\u00eb gabim, ose moskonsistenc\u00eb midis emrave t\u00eb skedarit dhe procedur\u00ebs s\u00eb ruajtur, at\u00ebher\u00eb deployDump<\/code> nuk do t\u00eb ekzekutohet, duke shfaqur tekstin e gabimit. Moskonsistenca e procedurave t\u00eb ruajtura midis dumpit dhe DB aktuale \u00ebsht\u00eb e pamundur n\u00eb p\u00ebrdorimin e deployDump<\/code>.<\/p>\n

    <\/p>\n

    Kur krijoni nj\u00eb procedur\u00eb t\u00eb re t\u00eb ruajtur, nuk \u00ebsht\u00eb e nevojshme t\u00eb futni manualisht emrin e sakt\u00eb t\u00eb skedarit. Mjafton q\u00eb skedari t\u00eb ket\u00eb zgjerimin .sql<\/code>. Pas thirrjes s\u00eb deployDump<\/code> teksti i gabimit do t\u00eb p\u00ebrmbaj\u00eb emrin e sakt\u00eb, i cili mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb riem\u00ebruar skedarin.<\/p><\/blockquote>\n

    deployDump<\/code> lejon t\u00eb ndryshosh parametrat e funksionit ose tipin e kthimit pa veprime t\u00eb tjera, nd\u00ebrsa n\u00eb qasjen klasike do t\u00eb duhej t\u00eb
    \nfillimisht t\u00eb ekzekutoje DROP FUNCTION<\/code>, dhe vet\u00ebm pastaj CREATE OR REPLACE FUNCTION<\/code>.<\/p>\n

    <\/p>\n

    Fatkeq\u00ebsisht, ekzistojn\u00eb disa situata ku deployDump<\/code> nuk mund t\u00eb zbatoj\u00eb automatikisht ndryshimet. P\u00ebr shembull, n\u00ebse hiqet nj\u00eb funksion ndikues q\u00eb p\u00ebrdoret nga t\u00eb pakt\u00ebn nj\u00eb ndikues tjet\u00ebr. T\u00eb tilla situata zgjidhen manualisht duke p\u00ebrdorur skedar\u00eb migrimi.<\/p>\n

    <\/p>\n

    N\u00ebse p\u00ebr transferimin e ndryshimeve n\u00eb procedurat e ruajtura \u00ebsht\u00eb p\u00ebrgjegj\u00ebs vet\u00eb schema-keeper<\/a><\/noindex>, at\u00ebher\u00eb p\u00ebr transferimin e ndryshimeve t\u00eb tjera n\u00eb struktur\u00eb \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrdoren skedar\u00eb migrimi. P\u00ebr shembull, nj\u00eb bibliotek\u00eb e mir\u00eb p\u00ebr t\u00eb punuar me migrimet \u00ebsht\u00eb doctrine\/migrations<\/a><\/noindex>.<\/p>\n

    <\/p>\n

    Migrimet duhet t\u00eb aplikohen para nisjes deployDump<\/code>. Kjo lejon b\u00ebj t\u00eb gjitha ndryshimet n\u00eb struktur\u00eb dhe t\u00eb zgjidh problemet, n\u00eb m\u00ebnyr\u00eb q\u00eb ndryshimet n\u00eb procedurat e ruajtura m\u00eb pas t\u00eb transferohen pa probleme.<\/p>\n

    <\/p>\n

    M\u00eb holl\u00ebsisht, puna me migrimet do t\u00eb p\u00ebrshkruhet n\u00eb kapitujt e ardhsh\u00ebm.<\/p>\n

    <\/p>\n

    Si t\u00eb organizohet procesi i pun\u00ebs paralele t\u00eb disa zhvilluesve n\u00eb projekt<\/h2>\n

    <\/p>\n

    Duhet t\u00eb krijohet nj\u00eb skript p\u00ebr inicializimin e plot\u00eb t\u00eb DB, i cili do t\u00eb aktivizohet nga zhvilluesi n\u00eb makin\u00eb e tij t\u00eb pun\u00ebs, duke sjell\u00eb struktur\u00ebn e DB lokale n\u00eb p\u00ebrputhje me dump-in e ruajtur n\u00eb VCS. M\u00eb s\u00eb lehti \u00ebsht\u00eb t\u00eb ndajm\u00eb inicializimin e DB lokale n\u00eb 3 hapa:<\/p>\n

    <\/p>\n

      \n
    1. Importimi i skedarit me struktur\u00ebn baz\u00eb, i cili do t\u00eb quhet, p\u00ebr shembull, base.sql<\/code> <\/li>\n
    2. Zbatimi i migrimeve<\/li>\n
    3. Thirrja deployDump<\/code><\/li>\n<\/ol>\n

      <\/p>\n

      base.sql<\/code> \u2014 kjo \u00ebsht\u00eb pika e nisjes, mbi t\u00eb cil\u00ebn zbatohen migrimet dhe ekzekutohet deployDump<\/code>, q\u00eb do t\u00eb thot\u00eb base.sql + migrimet + deployDump = struktura aktuale e DB<\/code>. Nj\u00eb skedar t\u00eb till\u00eb mund ta formoni p\u00ebrmes utilitarit pg_dump<\/code>. P\u00ebrdoret base.sql<\/code> p\u00ebr her\u00eb t\u00eb par\u00eb kur inicializohet baza e t\u00eb dh\u00ebnave nga zero.<\/p><\/blockquote>\n

      Ta quajm\u00eb skriptin p\u00ebr inicializimin e plot\u00eb t\u00eb DB refresh.sh<\/code>. Procesi i pun\u00ebs mund t\u00eb duket si m\u00eb posht\u00eb:<\/p>\n

      <\/p>\n

        \n
      1. Zhvilluesi aktivizon n\u00eb mjedisin e tij refresh.sh<\/code> dhe merr struktur\u00ebn aktuale t\u00eb DB<\/li>\n
      2. Zhvilluesi fillon t\u00eb punoj\u00eb mbi detyr\u00ebn e dh\u00ebn\u00eb, duke modifikuar DB lokale sipas nevojave t\u00eb funksionalitetit t\u00eb ri (ALTER TABLE ... ADD COLUMN<\/code> etj.)<\/li>\n
      3. Pas p\u00ebrfundimit t\u00eb detyr\u00ebs, zhvilluesi th\u00ebrret funksionin saveDump<\/code>, p\u00ebr t\u00eb regjistruar n\u00eb VCS ndryshimet e b\u00ebra n\u00eb DB<\/li>\n
      4. Zhvilluesi ekzekuton s\u00ebrish refresh.sh<\/code>, pastaj verifyDump<\/code>, i cili tani tregon nj\u00eb list\u00eb ndryshimesh p\u00ebr p\u00ebrfshirje n\u00eb migrim<\/li>\n
      5. Zhvilluesi transferon t\u00eb gjitha ndryshimet e struktur\u00ebs n\u00eb skedarin e migrimit, ekzekuton s\u00ebrish refresh.sh<\/code> dhe verifyDump<\/code>, dhe, n\u00ebse migrimi \u00ebsht\u00eb p\u00ebrgatitur sakt\u00eb, verifyDump<\/code> do t\u00eb tregoj\u00eb munges\u00ebn e ndryshimeve mes DB lokale dhe dump-it t\u00eb ruajtur<\/li>\n<\/ol>\n

        <\/p>\n

        Procesi i p\u00ebrshkruar m\u00eb sip\u00ebr \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm me parimet gitflow. \u00c7do deg\u00eb n\u00eb VCS do t\u00eb p\u00ebrmbaj\u00eb versionin e saj t\u00eb dump-it, dhe kur bashkohen deg\u00ebt, bashkohen edhe dump-et. N\u00eb shumic\u00ebn e rasteve, pas bashkimit nuk k\u00ebrkohet asnj\u00eb veprim shtes\u00eb, por n\u00ebse jan\u00eb b\u00ebr\u00eb ndryshime n\u00eb deg\u00eb t\u00eb ndryshme, p\u00ebr shembull, n\u00eb t\u00eb nj\u00ebjt\u00ebn tabel\u00eb, mund t\u00eb ndodhi nj\u00eb konflikt.<\/p>\n

        <\/p>\n

        Le t\u00eb shqyrtojm\u00eb nj\u00eb situat\u00eb konfliktuese me shembuj: ka nj\u00eb deg\u00eb develop<\/em>, nga e cila dalin dy deg\u00eb: feature1<\/em> dhe feature2<\/em>, t\u00eb cilat nuk kan\u00eb konflikte me develop<\/em>, por kan\u00eb konflikte mes tyre. \u00cbsht\u00eb krijuar detyra p\u00ebr t\u00eb bashkuar t\u00eb dy deg\u00ebt n\u00eb develop<\/em>. P\u00ebr k\u00ebt\u00eb rast rekomandohet fillimisht t\u00eb bashkohet nj\u00eb nga deg\u00ebt n\u00eb develop<\/em>, dhe pastaj bashkimi develop<\/em> n\u00eb deg\u00ebn tjet\u00ebr, duke zgjidhur n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb konfliktet n\u00eb deg\u00ebn tjet\u00ebr, pas s\u00eb cil\u00ebs b\u00ebhet bashkimi i deg\u00ebs s\u00eb fundit n\u00eb develop<\/em>. N\u00eb faz\u00ebn e zgjidhjes s\u00eb konflikteve, mund t\u00eb nevojitet t\u00eb korrigjohet skedari i migrimit n\u00eb deg\u00ebn e fundit, n\u00eb m\u00ebnyr\u00eb q\u00eb ai t\u00eb p\u00ebrputhet me dump-in p\u00ebrfundimtar, q\u00eb p\u00ebrfshin rezultatet e bashkimeve.<\/p>\n

        <\/p>\n

        Si t\u00eb depozitohen n\u00eb m\u00ebnyr\u00eb t\u00eb sigurt\u00eb nj\u00eb num\u00ebr t\u00eb madh t\u00eb ndryshimeve n\u00eb struktur\u00ebn e DB n\u00eb mjedisin production<\/h2>\n

        <\/p>\n

        Fal\u00eb pranis\u00eb n\u00eb VCS t\u00eb dump-it t\u00eb struktur\u00ebs aktuale t\u00eb DB, shfaqet mund\u00ebsia p\u00ebr t\u00eb verifikuar baz\u00ebn e prodhimit p\u00ebr p\u00ebrputhshm\u00ebrin\u00eb e sakt\u00eb me struktur\u00ebn e k\u00ebrkuar. Kjo garanton se t\u00eb gjitha ndryshimet q\u00eb jan\u00eb menduar nga zhvilluesit jan\u00eb transferuar me sukses n\u00eb baz\u00ebn e prodhimit.<\/p>\n

        <\/p>\n

        Sepse DDL<\/a><\/noindex> n\u00eb PostgreSQL \u00ebsht\u00eb transaksionale<\/a><\/noindex>, rekomandohet t\u00eb respektohet rendi i m\u00ebposht\u00ebm i publikimit, n\u00eb m\u00ebnyr\u00eb q\u00eb, n\u00eb rast t\u00eb nj\u00eb gabimi t\u00eb papritur, t\u00eb b\u00ebhet \"pa dhimbje\" RIVENDOS<\/code>:<\/p>\n

        <\/p>\n

          \n
        1. Filloni transaksionin<\/li>\n
        2. N\u00eb transaksion t\u00eb zbatohen t\u00eb gjitha migrimet<\/li>\n
        3. N\u00eb t\u00eb nj\u00ebjtin transaksion t\u00eb ekzekutohet deployDump<\/code><\/li>\n
        4. . Pa e p\u00ebrfunduar transaksionin, t\u00eb ekzekutohet verifyDump<\/code>. N\u00ebse nuk ka gabime, t\u00eb ekzekutohet COMMIT<\/code>. N\u00ebse ka gabime, t\u00eb ekzekutohet RIVENDOS<\/code><\/li>\n<\/ol>\n

          <\/p>\n

          K\u00ebto hapa jan\u00eb mjaft leht\u00ebsisht t\u00eb inkorporuar n\u00eb qasjet ekzistuese t\u00eb publikimit t\u00eb aplikacioneve, duke p\u00ebrfshir\u00eb zero-downtime.<\/p>\n

          <\/p>\n

          P\u00ebrfundimi<\/h1>\n

          <\/p>\n

          Fal\u00eb metodave t\u00eb p\u00ebrshkruara m\u00eb sip\u00ebr, mund t\u00eb nxirret maksimumi i performanc\u00ebs nga projektet \"PHP + PostgreSQL\", duke sakrifikuar n\u00eb at\u00eb m\u00ebnyr\u00eb nj\u00eb sasi relativisht t\u00eb vog\u00ebl t\u00eb leht\u00ebsis\u00eb s\u00eb zhvillimit krahasuar me realizimin e gjith\u00eb logjik\u00ebs s\u00eb biznesit n\u00eb kodin kryesor t\u00eb aplikacionit. M\u00eb shum\u00eb, p\u00ebrpunimi i t\u00eb dh\u00ebnave n\u00eb PL\/pgSQL<\/a><\/noindex> shpesh duket m\u00eb transparent dhe k\u00ebrkon nj\u00eb sasi m\u00eb t\u00eb vog\u00ebl kodi, sesa funksionaliteti i nj\u00ebjt\u00eb, i shkruar n\u00eb PHP.<\/p>\n

          Burimi: 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\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\udd47Logjika e biznesit n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave me ndihm\u00ebn e SchemaKeeper | ProHoster","description":"Q\u00ebllimi i k\u00ebtij artikulli \u00ebsht\u00eb t\u00eb tregoj\u00eb, p\u00ebrmes bibliotek\u00ebs schema-keeper, mjetet q\u00eb leht\u00ebsojn\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb konsiderueshme procesin e zhvillimit t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave n\u00eb projektet PHP q\u00eb p\u00ebrdorin DBMS PostgreSQL. Informacioni n\u00eb k\u00ebt\u00eb artikull do t\u00eb jet\u00eb sidomos i dobish\u00ebm p\u00ebr zhvilluesit q\u00eb d\u00ebshirojn\u00eb t\u00eb shfryt\u00ebzojn\u00eb n\u00eb maksimum mund\u00ebsit\u00eb e PostgreSQL, por hasin probleme me ruajtjen e logjik\u00ebs s\u00eb biznesit n\u00eb DB. Artikulli nuk do t\u00eb p\u00ebrshkruaj\u00eb avantazhet","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/biznes-logika-v-baze-dannyh-pri-pomoshhi-schemakeeper","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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 \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","og:url":"https:\/\/prohoster.info\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/31385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=31385"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31385\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=31385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=31385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=31385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}