{"id":36650,"date":"2019-10-31T22:12:54","date_gmt":"2019-10-31T19:12:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/tranzaktsii-v-globalah-intersystems-iris\/"},"modified":"2019-10-31T22:12:54","modified_gmt":"2019-10-31T19:12:54","slug":"tranzaktsii-v-globalah-intersystems-iris","status":"publish","type":"post","link":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/tranzaktsii-v-globalah-intersystems-iris","title":{"rendered":"Transakcije u globalima InterSystems IRIS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Transakcije u globalima InterSystems IRIS\" src=\"\/wp-content\/uploads\/2019\/07\/ee4e58369616511dc213f94158b04e4f.jpg\" style=\"display:block;margin: 0 auto;\" \/>Sistem upravljanja bazama podataka InterSystems IRIS podr\u017eava zanimljive strukture za skladi\u0161tenje podataka - globalne. U su\u0161tini, ovo su vi\u0161eslojne klju\u010deve sa raznim dodatnim funkcijama poput transakcija, brzih funkcija za pretra\u017eivanje drve\u0107a podataka, blokada i svog jezika ObjectScript.<\/p>\n<p>Vi\u0161e o globalima u seriji \u010dlanaka \u00abGlobali - ma\u010devi za skladi\u0161tenje podataka\u00bb:<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/intersystems\/blog\/263791\/\">Drve\u0107a. Deo 1<\/a><\/noindex> <br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/intersystems\/blog\/264173\/\">Drve\u0107a. Deo 2<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/intersystems\/blog\/268465\/\">Sparsi nizovi. Deo 3<\/a><\/noindex><\/p>\n<p>Zanima me kako su implementirane transakcije u globalima, koje su njihove karakteristike. Jer to je potpuno druga\u010dija struktura za skladi\u0161tenje podataka u pore\u0111enju sa svima poznatim tabelama. Mnogo je na ni\u017eem nivou.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nKao \u0161to je poznato iz teorije relacijskih baza podataka, dobra implementacija transakcija treba da zadovoljava zahteve <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/ACID\">ACID<\/a><\/noindex>:<\/p>\n<p><b>A - Atomarnost.<\/b> Svi promenjeni podaci u transakciji moraju biti zabele\u017eeni ili nijedna izmena ne sme biti sa\u010duvana.<\/p>\n<p><b>S - doslednost.<\/b> Nakon zavr\u0161etka transakcije, logi\u010dko stanje baze podataka mora biti interno konzistentno. U velikoj meri, ovaj zahtev se odnosi na programera, ali u slu\u010daju SQL baza podataka tako\u0111e se ti\u010de stranih klju\u010deva.<\/p>\n<p><b>I - izolovanost.<\/b> Paralelno izvr\u0161ene transakcije ne smeju imati uticaj jedna na drugu.<\/p>\n<p><b>D - trajnost.<\/b> Nakon uspe\u0161nog zavr\u0161etka transakcije, problemi na ni\u017eim nivoima (npr. prekid napajanja) ne bi trebali imati uticaj na podatke koji su promenjeni tokom transakcije.<\/p>\n<p>Globali su nerelacione strukture podataka. Kreirani su za veoma brzu upotrebu na veoma ograni\u010denom hardveru. Hajde da istra\u017eimo implementaciju transakcija u globalima pomo\u0107u <noindex><a rel=\"nofollow\" href=\"https:\/\/hub.docker.com\/_\/intersystems-iris-data-platform\/plans\/222f869e-567c-4928-b572-eb6a29706fbd?tab=instructions\">slu\u017ebenog docker imid\u017ea IRIS<\/a><\/noindex>.<\/p>\n<p>Za podr\u0161ku transakcijama u IRIS-u koriste se komande: <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.intersystems.com\/irislatest\/csp\/docbook\/DocBook.UI.Page.cls?KEY=RCOS_ctstart\">TSTART<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.intersystems.com\/irislatest\/csp\/docbook\/DocBook.UI.Page.cls?KEY=RCOS_ctcommit\">TCOMMIT<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.intersystems.com\/irislatest\/csp\/docbook\/DocBook.UI.Page.cls?KEY=RCOS_ctrollback\">TROLLBACK<\/a><\/noindex>.<\/p>\n<h2>1. Atomarnost<\/h2>\n<p>\nNajlak\u0161e je proveriti atomarnost. Proveravamo iz konzole baze podataka.<\/p>\n<pre><code class=\"bash\">Kill ^a\nTSTART\nSet ^a(1) = 1\nSet ^a(2) = 2\nSet ^a(3) = 3\nTCOMMIT<\/code><\/pre>\n<p>\nNakon toga radimo proveru:<\/p>\n<pre><code class=\"bash\">Write ^a(1), \u201c \u201d, ^a(2), \u201c \u201d, ^a(3)<\/code><\/pre>\n<p>\nDobijamo:<\/p>\n<pre><code class=\"bash\">1 2 3<\/code><\/pre>\n<p>\nSve je u redu. Atomarnost je o\u010duvana: sve izmene su sa\u010duvane.<\/p>\n<p>Pove\u0107amo te\u017einu zadatka, unesemo gre\u0161ku i vidimo kako \u0107e se transakcija sa\u010duvati, delimi\u010dno ili uop\u0161te.<\/p>\n<p>Jo\u0161 jednom proveravamo atomarnost:<\/p>\n<pre><code class=\"bash\">Kill ^A\nTSTART\nSet ^a(1) = 1\nSet ^a(2) = 2\nSet ^a(3) = 3<\/code><\/pre>\n<p>\nNakon toga, prisilno \u0107emo zaustaviti kontejner, pokrenuti ga i pogledati. <\/p>\n<pre><code class=\"bash\">docker kill my-iris<\/code><\/pre>\n<p>\nOva komanda je prakti\u010dno ekvivalentna nasilnom isklju\u010divanju napajanja, jer \u0161alje signal za trenutni prekid procesa SIGKILL.<\/p>\n<p>Mo\u017eda je transakcija sa\u010duvana delimi\u010dno?<\/p>\n<pre><code class=\"bash\">WRITE ^a(1), ^a(2), ^a(3)\n^\n ^a(1)<\/code><\/pre>\n<p>\n \u2014 Ne, nije sa\u010duvana.<\/p>\n<p>Isproba\u0107emo komandu za vra\u0107anje:<\/p>\n<pre><code class=\"bash\">Kill ^A\nTSTART\nSet ^a(1) = 1\nSet ^a(2) = 2\nSet ^a(3) = 3\nTROLLBACK\n\nWRITE ^a(1), ^a(2), ^a(3)\n^\n ^a(1)<\/code><\/pre>\n<p>\nTako\u0111e ni\u0161ta nije sa\u010duvano.<\/p>\n<h2>2. Konzistentnost<\/h2>\n<p>\nBudu\u0107i da se u bazama na globalima klju\u010devi prave tako\u0111e na globalima (podse\u0107am, global je struktura za skladi\u0161tenje podataka na ni\u017eem nivou od relacione tabele), za ispunjavanje zahteva za konzistentnost potrebno je uklju\u010diti promenu klju\u010da u istu transakciju kao i promenu globalne.<\/p>\n<p>Na primer, imamo global ^person, u kojem \u010duvamo li\u010dne podatke i kao klju\u010d koristimo PIB.<\/p>\n<pre><code class=\"bash\">^person(1234567, \u2018firstname\u2019) = \u2018Sergey\u2019\n^person(1234567, \u2018lastname\u2019) = \u2018Kamenev\u2019\n^person(1234567, \u2018phone\u2019) = \u2018+74995555555\n...<\/code><\/pre>\n<p>\nDa bismo imali brz pretra\u017eivanje po prezimenu i imenu, napravili smo klju\u010d ^index.<\/p>\n<pre><code class=\"bash\">^index(\u2018Kamenev\u2019, \u2018Sergey\u2019, 1234567) = 1<\/code><\/pre>\n<p>\nKako bi baza bila konzistentna, moramo dodavati li\u010dne podatke na slede\u0107i na\u010din:<\/p>\n<pre><code class=\"bash\">TSTART\n^person(1234567, \u2018firstname\u2019) = \u2018Sergey\u2019\n^person(1234567, \u2018lastname\u2019) = \u2018Kamenev\u2019\n^person(1234567, \u2018phone\u2019) = \u2018+74995555555\n^index(\u2018Kamenev\u2019, \u2018Sergey\u2019, 1234567) = 1\nTCOMMIT<\/code><\/pre>\n<p>\nS obzirom na to, prilikom brisanja tako\u0111e moramo koristiti transakciju:<\/p>\n<pre><code class=\"bash\">TSTART\nKill ^person(1234567)\nZKill ^index(\u2018Kamenev\u2019, \u2018Sergey\u2019, 1234567)\nTCOMMIT<\/code><\/pre>\n<p>\nDrugim re\u010dima, ispunjenje zahteva za konzistentnost le\u017ei potpuno na ramenima programera. Ali kada je re\u010d o globalima \u2014 to je normalno, zbog njihove niskonivojske prirode.<\/p>\n<h2>3. Izolacija<\/h2>\n<p>\nTada po\u010dinju zamr\u0161enosti. Mnogi korisnici istovremeno rade na istoj bazi, menjaju iste podatke.<\/p>\n<p>Situacija se mo\u017ee uporediti sa tim kada vi\u0161e korisnika istovremeno radi sa istim repozitorijumom koda i poku\u0161ava da istovremeno komituju promene u mnogim fajlovima odjednom.<\/p>\n<p>Baza podataka mora da re\u0161ava sve ovo u realnom vremenu. S obzirom na to da u ozbiljnim kompanijama postoji \u010dak i specijalna osoba koja odgovara za kontrolu verzija (za spajanje grana, re\u0161avanje konflikata itd.), a Baza podataka sve ovo treba da radi u realnom vremenu, postaje o\u010digledna slo\u017eenost zadatka i ispravnost projektovanja baze podataka i koda koji je odr\u017eava.<\/p>\n<p>Baza podataka ne mo\u017ee razumjeti smisao radnji koje korisnici poduzimaju kako bi sprije\u010dila sukobe ako rade s istim podacima. Ona mo\u017ee samo poni\u0161titi jednu transakciju koja je u suprotnosti s drugom ili ih izvr\u0161iti uzastopno.<\/p>\n<p>Jo\u0161 jedan problem je \u0161to tokom izvr\u0161enja transakcije (prije commit-a) stanje baze mo\u017ee biti nesaglasno, pa je po\u017eeljno da druge transakcije nemaju pristup nesaglasnom stanju baze podataka, \u0161to se posti\u017ee u relacijskim DB na mnoge na\u010dine: stvaranjem snimaka, vi\u0161ekratnom verzioniranjem redova itd.<\/p>\n<p>Pri paralelnom izvr\u0161avanju transakcija va\u017eno je da se one ne ometaju me\u0111usobno. To je i svojstvo izolacije.<\/p>\n<p>SQL defini\u0161e 4 nivoa izolacije:<\/p>\n<ul>\n<li>READ UNCOMMITTED<\/li>\n<li>READ COMMITTED<\/li>\n<li>REPEATABLE READ<\/li>\n<li>SERIALIZABLE<\/li>\n<\/ul>\n<p>\nRazmotrimo svaki nivo posebno. Tro\u0161kovi implementacije svakog nivoa rastu gotovo eksponencijalno.<\/p>\n<p><b>READ UNCOMMITTED<\/b> \u2014 to je najni\u017ei nivo izolacije, ali ujedno i najbr\u017ei. Transakcije mogu \u010ditati promjene koje su jedna drugoj unijele.<\/p>\n<p><b>READ COMMITTED<\/b> \u2014 to je slede\u0107i nivo izolacije koji predstavlja kompromis. Transakcije ne mogu \u010ditati promjene koje su jedna drugoj unijele do commit-a, ali mogu \u010ditati sve promjene unijete nakon commit-a.<\/p>\n<p>Ako imamo dugu transakciju T1, tokom koje su izvr\u0161eni commit-i u transakcijama T2, T3\u2026 Tn, koje su radile s istim podacima kao T1, onda \u0107emo pri zahtjevu za podacima u T1 svaki put dobijati razli\u010dit rezultat. Ovaj fenomen se naziva neponovljivo \u010ditanje.<\/p>\n<p><b>REPEATABLE READ<\/b> \u2014 na ovom nivou izolacije nemamo fenomen neponovljivog \u010ditanja, zahvaljuju\u0107i tome \u0161to se za svaki zahtjev za \u010ditanje podataka stvara snimak rezultata podataka i pri ponovnom kori\u0161tenju u ovoj istoj transakciji koristi se podataka iz snimka. Me\u0111utim, na ovom nivou izolacije mo\u017ee do\u0107i do \u010ditanja fantomskih podataka. Misli se na \u010ditanje novih redova koji su dodani paralelnim fiksiranim transakcijama.<\/p>\n<p><b>SERIALIZABLE<\/b> \u2014 najvi\u0161i nivo izolacije. Karakteri\u0161e se time da podaci na bilo koji na\u010din kori\u0161\u0107eni u transakciji (\u010ditanje ili izmjena) postaju dostupni drugim transakcijama tek nakon zavr\u0161etka prve transakcije.<\/p>\n<p>Prvo \u0107emo razjasniti postoji li izolacija operacija u transakciji od glavnog toka. Otvorimo 2 terminalna prozora.<\/p>\n<pre><code class=\"bash\">Kill ^t\n\nWrite ^t(1)\n2<\/code><\/pre>\n<pre><code class=\"bash\">\nTSTART\nSet ^t(1)=2<\/code><\/pre>\n<p>\nNema izolacije. Jedan tok vidi \u0161to drugi radi dok otvara transakciju.<\/p>\n<p>Pogledajmo vide li transakcije razli\u010ditih tokova ono \u0161to se de\u0161ava unutar njih. <\/p>\n<p>Otvorimo 2 terminalna prozora i otvorimo 2 transakcije paralelno.<\/p>\n<pre><code class=\"bash\">kill ^t\nTSTART\nWrite ^t(1)\n3<\/code><\/pre>\n<pre><code class=\"bash\">\nTSTART\nSet ^t(1)=3\n<\/code><\/pre>\n<p>\nParalelne transakcije vide jedni druge podatke. Dakle, dobili smo najjednostavniju, ali i najbr\u017eu razinu izolacije READ UNCOMMITTED.<\/p>\n<p>U principu, to se moglo o\u010dekivati za globalne varijable, za koje se uvijek nagla\u0161avala brzina. <\/p>\n<p>\u0160to u\u010diniti ako nam zatreba vi\u0161a razina izolacije u operacijama sa globalnim varijablama?<\/p>\n<p>Ovde treba razmisliti za\u0161to su uop\u0161te potrebne razine izolacije i kako one funkcioni\u0161u.<\/p>\n<p>Najvi\u0161a razina izolacije SERIALIZE zna\u010di da je rezultat paralelno izvr\u0161avanih transakcija ekvivalentan njihovom sekvencijalnom izvr\u0161avanju, \u0161to garantuje odsustvo kolizija.<\/p>\n<p>To mo\u017eemo posti\u0107i putem pametnog zaklju\u010davanja u ObjectScript, koje ima mnogo razli\u010ditih na\u010dina primene: mo\u017ee se praviti obi\u010dno, inkrementalno, vi\u0161estruko zaklju\u010davanje komandom <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.intersystems.com\/latest\/csp\/docbook\/DocBook.UI.Page.cls?KEY=RCOS_clock\">LOCK<\/a><\/noindex>.<\/p>\n<p>Ni\u017ee razine izolacije su kompromisi koji imaju za cilj pove\u0107ati brzinu rada baze podataka.<\/p>\n<p>Pogledajmo kako mo\u017eemo posti\u0107i razli\u010dite razine izolacije putem zaklju\u010davanja.<\/p>\n<p>Ova komanda omogu\u0107ava ne samo ekskluzivna zaklju\u010davanja koja su potrebna za promenu podataka, ve\u0107 i takozvana shared zaklju\u010davanja koja mogu istovremeno uzeti vi\u0161e tokova kada im je potrebno da \u010ditaju podatke koji ne bi trebali biti menjani od strane drugih procesa tokom \u010ditanja.<\/p>\n<p>Vi\u0161e informacija o dvostrukom metodolo\u0161kom zaklju\u010davanju na ruskom i engleskom jeziku:<\/p>\n<p>\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%94%D0%B2%D1%83%D1%85%D1%84%D0%B0%D0%B7%D0%BD%D0%B0%D1%8F_%D0%B1%D0%BB%D0%BE%D0%BA%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0\">Dvostruko zaklju\u010davanje<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Two-phase_locking\">Two-phase locking<\/a><\/noindex><\/p>\n<p>Te\u0161ko\u0107a le\u017ei u tome \u0161to stanje baze tokom transakcije mo\u017ee biti nesaglasno, me\u0111utim ti nesaglasni podaci su vidljivi drugim procesima. Kako to izbe\u0107i?<\/p>\n<p>Napravi\u0107emo taka vidna okna pomo\u0107u zaklju\u010davanja u kojima \u0107e stanje baze biti uskla\u0111eno. I svi pristupi tim vidnim oknima uskla\u0111enog stanja bi\u0107e kontrolisani zaklju\u010davanjima.<\/p>\n<p>Deljene blokade istih podataka su vi\u0161ekratne \u2014 njih mogu uzeti vi\u0161e procesa. Ove blokade zabranjuju drugim procesima da menjaju podatke, tj. koriste se za formiranje prozora doslednog stanja baze podataka.<\/p>\n<p>Ekskluzivne blokade se koriste za izmenu podataka \u2014 takvu blokadu mo\u017ee uzeti samo jedan proces. Ekskluzivnu blokadu mo\u017ee uzeti:<\/p>\n<ol>\n<li>Svaki proces, ako su podaci slobodni<\/li>\n<li>Samo onaj proces koji ima shared blokadu na tim podacima i koji je prvi zatra\u017eio ekskluzivnu blokadu.<\/li>\n<\/ol>\n<p>\n<img decoding=\"async\" alt=\"Transakcije u globalima InterSystems IRIS\" src=\"\/wp-content\/uploads\/2019\/07\/bb91ed1268925bc1b9266763ab82646a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u0160to je u\u017ei prozor vidljivosti, to du\u017ee treba drugim procesima da \u010dekaju, ali stanje baze podataka u njemu mo\u017ee biti doslednije.<\/p>\n<p><b>READ_COMMITTED<\/b> \u2014 su\u0161tina ovog nivoa je da vidimo samo potvr\u0111ene podatke iz drugih tokova. Ako podaci u drugoj transakciji jo\u0161 nisu potvr\u0111eni, onda vidimo njihovu staru verziju.<\/p>\n<p>To nam omogu\u0107ava da paralelizujemo rad umesto da \u010dekamo osloba\u0111anje blokade.<\/p>\n<p>Bez posebnih trikova ne\u0107emo mo\u0107i da vidimo staru verziju podataka u IRIS-u, zato \u0107emo morati da se sna\u0111emo s blokadama.<\/p>\n<p>Prema tome, mora\u0107emo da omogu\u0107imo \u010ditanje podataka samo u trenucima doslednosti putem shared blokada.<\/p>\n<p>Recimo da imamo bazu korisnika ^person, koji me\u0111usobno prebacuju novac.<\/p>\n<p>Momenat prebacivanja od osobe 123 ka osobi 242:<\/p>\n<pre><code class=\"bash\">LOCK +^person(123), +^person(242)\nSet ^person(123, amount) = ^person(123, amount) - amount\nSet ^person(242, amount) = ^person(242, amount) + amount\nLOCK -^person(123), -^person(242)<\/code><\/pre>\n<p>\nMomenat zahteva koli\u010dine novca osobe 123 pre otpisa mora biti pra\u0107en ekskluzivnom blokadom (po defaultu):<\/p>\n<pre><code class=\"bash\">LOCK +^person(123)\nWrite ^person(123)<\/code><\/pre>\n<p>\nA ako treba prikazati stanje ra\u010duna u li\u010dnom nalogu, mo\u017ee se koristiti shared blokada ili \u010dak uop\u0161te ne koristiti:<\/p>\n<pre><code class=\"bash\">LOCK +^person(123)#\u201dS\u201d\nWrite ^person(123)<\/code><\/pre>\n<p>\nMe\u0111utim, ako pretpostavimo da operacije sa bazom podataka izvr\u0161avaju prakti\u010dno odmah (podse\u0107am, globali su mnogo nizak nivo struktura u pore\u0111enju sa relacijskom tabelom), potreba za ovim nivoom opada.<\/p>\n<p><b>REPEATABLE READ<\/b> \u2014 na ovom nivou izolacije dopu\u0161teno je da se mo\u017ee dogoditi vi\u0161e \u010ditanja podataka koji se mogu menjati paralelnim transakcijama. <\/p>\n<p>Prema tome, mora\u0107emo da postavimo shared blokadu za \u010ditanje podataka koje menjamo i ekskluzivne blokade za podatke koje menjamo.<\/p>\n<p>Operator LOCK allows you to detail all necessary locks in one operator, which can be very numerous.<\/p>\n<pre><code class=\"bash\">LOCK +^person(123, amount)#\u201dS\u201d\nreading ^person(123, amount)<\/code><\/pre>\n<p>\nother operations (meanwhile, parallel processes try to modify ^person(123, amount), but cannot)<\/p>\n<pre><code class=\"bash\">LOCK +^person(123, amount)\nmodifying ^person(123, amount)\nLOCK -^person(123, amount)\n\nreading ^person(123, amount)\nLOCK -^person(123, amount)#\u201dS\u201d<\/code><\/pre>\n<p>\nWhen listing locks separated by commas, they are obtained sequentially, but if done like this:<\/p>\n<pre><code class=\"bash\">LOCK +(^person(123),^person(242))<\/code><\/pre>\n<p>\nthey are obtained atomically all at once.<\/p>\n<p><b>SERIALIZE<\/b> \u2014 we will have to set locks in such a way that ultimately all transactions that share data are executed sequentially. For this approach, most locks must be exclusive and taken on the smallest areas of the global for performance.<\/p>\n<p>If we talk about withdrawals from global ^person, then only SERIALIZE isolation level is acceptable for it, as money must be spent strictly sequentially; otherwise, it is possible to spend the same amount multiple times.<\/p>\n<h2>4. Durability<\/h2>\n<p>\nI conducted tests with a hard shutdown of the container through<\/p>\n<pre><code class=\"bash\">docker kill my-iris<\/code><\/pre>\n<p>\nThe database handled well. No problems were identified.<\/p>\n<h2>Zaklju\u010dak<\/h2>\n<p>\nFor globals in InterSystems IRIS, transaction support is available. They are indeed atomic and reliable. To ensure database consistency in globals, programmer effort and transaction usage are required, as there are no complex built-in constructs like foreign keys.<\/p>\n<p>The isolation level of globals without using locks is READ UNCOMMITTED, but with locks, it can be ensured up to SERIALIZE level.<\/p>\n<p>The correctness and speed of transactions on globals heavily depend on the programmer's skill: the broader the use of shared locks during reading, the higher the isolation level, and the narrower the exclusive locks are taken, the greater the performance.<br \/>\n<br \/>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/461753\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0421\u0423\u0411\u0414 InterSystems IRIS \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442 \u043b\u044e\u0431\u043e\u043f\u044b\u0442\u043d\u044b\u0435 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u0434\u043b\u044f \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445 \u2014 \u0433\u043b\u043e\u0431\u0430\u043b\u044b. \u041f\u043e \u0441\u0443\u0442\u0438 \u044d\u0442\u043e \u043c\u043d\u043e\u0433\u043e\u0443\u0440\u043e\u0432\u043d\u0435\u0432\u044b\u0435 \u043a\u043b\u044e\u0447\u0438 \u0441 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u043c\u0438 \u0434\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u043c\u0438 \u043f\u043b\u044e\u0448\u043a\u0430\u043c\u0438 \u0432 \u0432\u0438\u0434\u0435 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439, \u0431\u044b\u0441\u0442\u0440\u044b\u0445 \u0444\u0443\u043d\u043a\u0446\u0438\u0439 \u0434\u043b\u044f \u043e\u0431\u0445\u043e\u0434\u0430 \u0434\u0435\u0440\u0435\u0432\u044c\u0435\u0432 \u0434\u0430\u043d\u043d\u044b\u0445, \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043e\u043a \u0438 \u0441\u0432\u043e\u0435\u0433\u043e \u044f\u0437\u044b\u043a\u0430 ObjectScript. \u041f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0435 \u043e \u0433\u043b\u043e\u0431\u0430\u043b\u0430\u0445 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u0413\u043b\u043e\u0431\u0430\u043b\u044b \u2014 \u043c\u0435\u0447\u0438-\u043a\u043b\u0430\u0434\u0435\u043d\u0446\u044b \u0434\u043b\u044f \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445\u00bb: \u0414\u0435\u0440\u0435\u0432\u044c\u044f. \u0427\u0430\u0441\u0442\u044c 1 \u0414\u0435\u0440\u0435\u0432\u044c\u044f. \u0427\u0430\u0441\u0442\u044c 2 \u0420\u0430\u0437\u0440\u0435\u0436\u0435\u043d\u043d\u044b\u0435 \u043c\u0430\u0441\u0441\u0438\u0432\u044b. \u0427\u0430\u0441\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27448,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36650","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0421\u0423\u0411\u0414 InterSystems IRIS \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442 \u043b\u044e\u0431\u043e\u043f\u044b\u0442\u043d\u044b\u0435 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/tranzaktsii-v-globalah-intersystems-iris\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"bs_BA\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0422\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0438 \u0432 \u0433\u043b\u043e\u0431\u0430\u043b\u0430\u0445 InterSystems IRIS | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0421\u0423\u0411\u0414 InterSystems IRIS \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442 \u043b\u044e\u0431\u043e\u043f\u044b\u0442\u043d\u044b\u0435 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/tranzaktsii-v-globalah-intersystems-iris\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:12:54+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:12:54+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Transactions in Globals InterSystems IRIS | ProHoster","description":"The InterSystems IRIS DBMS supports interesting structures.","canonical_url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/tranzaktsii-v-globalah-intersystems-iris","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"bs_BA","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\u0422\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0438 \u0432 \u0433\u043b\u043e\u0431\u0430\u043b\u0430\u0445 InterSystems IRIS | ProHoster","og:description":"\u0421\u0423\u0411\u0414 InterSystems IRIS \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442 \u043b\u044e\u0431\u043e\u043f\u044b\u0442\u043d\u044b\u0435 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b.","og:url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/tranzaktsii-v-globalah-intersystems-iris","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-31T19:12:54+00:00","article:modified_time":"2019-10-31T19:12:54+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36650","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-22 04:17:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:41:52","updated":"2026-01-22 04:17:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/36650","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/comments?post=36650"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/36650\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media\/27448"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media?parent=36650"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/categories?post=36650"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/tags?post=36650"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}