{"id":120215,"date":"2024-10-17T19:09:08","date_gmt":"2024-10-17T17:09:08","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-subd-mysql-9-1-0"},"modified":"2024-10-17T19:09:08","modified_gmt":"2024-10-17T17:09:08","slug":"vypusk-subd-mysql-9-1-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/vypusk-subd-mysql-9-1-0","title":{"rendered":"L\u00ebshimi i SGBD-s\u00eb MySQL 9.1.0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Kompania Oracle ka formuar nj\u00eb deg\u00eb t\u00eb re t\u00eb DBMS MySQL 9.1.0. Nd\u00ebrtimet e MySQL Community Server 9.1.0 jan\u00eb p\u00ebrgatitur p\u00ebr t\u00eb gjitha distribucione kryesore t\u00eb Linux, FreeBSD, macOS dhe Windows. Si pjes\u00eb e modelit t\u00eb ri t\u00eb formimit t\u00eb l\u00ebshimeve t\u00eb vendosur vitin e kaluar, MySQL 9.1 i p\u00ebrket deg\u00ebve \u2018Innovation\u2019, n\u00eb t\u00eb cilat do t\u00eb p\u00ebrfshihet gjithashtu l\u00ebshimi i r\u00ebnd\u00ebsish\u00ebm i ardhsh\u00ebm MySQL 9.2. Deg\u00ebt Innovation rekomandohen p\u00ebr ata q\u00eb duan m\u00eb her\u00ebt akses n\u00eb funksionalitete t\u00eb reja, publikohen \u00e7do 3 muaj dhe mb\u00ebshteten vet\u00ebm deri n\u00eb l\u00ebshimin e l\u00ebshimit t\u00eb ardhsh\u00ebm t\u00eb r\u00ebnd\u00ebsish\u00ebm (p.sh., pas daljes s\u00eb deg\u00ebs 9.1, mb\u00ebshtetja e deg\u00ebs 9.0 nd\u00ebrpritet). N\u00eb ver\u00ebn e vitit t\u00eb ardhsh\u00ebm, planifikohet t\u00eb formohet nj\u00eb l\u00ebshim LTS, rekomanduar p\u00ebr zbatime q\u00eb k\u00ebrkojn\u00eb parashikueshm\u00ebri dhe ruajtje t\u00eb sjelljes s\u00eb pandryshuar p\u00ebr nj\u00eb periudh\u00eb t\u00eb gjat\u00eb. Pas deg\u00ebs LTS do t\u00eb formohet nj\u00eb deg\u00eb e re Innovation - MySQL 10.0. <\/p>\n
Ndryshimet kryesore n\u00eb MySQL 9.1: <\/p>\n
\n
Operacionit \u2018CREATE VIEW\u2019 i \u00ebsht\u00eb shtuar mb\u00ebshtetje p\u00ebr shprehjen \u2018IF NOT EXISTS\u2019, duke lejuar krijimin e pamjes vet\u00ebm n\u00ebse nj\u00eb pamje me emrin e dh\u00ebn\u00eb nuk ekziston ende dhe p\u00ebr t\u00eb shmangur kthimin e nj\u00eb gabimi n\u00ebse pamja tashm\u00eb \u00ebsht\u00eb krijuar.\n
Ngarkimi i treguesve \u00ebsht\u00eb nd\u00ebrprer\u00eb gjat\u00eb kryerjes s\u00eb operacioneve q\u00eb lidhen vet\u00ebm me leximin. M\u00eb par\u00eb, treguesit ngarkoheshin gjat\u00eb \u00e7do qasjeje n\u00eb tabel\u00eb, gj\u00eb q\u00eb shkaktonte konsumimin e memories dhe ngarkes\u00eb t\u00eb CPU-s\u00eb n\u00eb situata kur treguesit nuk ishin p\u00ebrdorur (p.sh., gjat\u00eb kryerjes s\u00eb pyetjeve SELECT). N\u00eb MySQL 9.1, p\u00ebrpunimi dhe ngarkimi i treguesve jan\u00eb ndar\u00eb n\u00eb dy faza: leximi i metadata-ve p\u00ebr treguesin dhe analizimi + ekzekutimi i treguesit. T\u00eb dh\u00ebnat e marra n\u00eb faz\u00ebn e par\u00eb ruahen nj\u00eb her\u00eb dhe pastaj shfryt\u00ebzohen p\u00ebr shembuj t\u00eb ndrysh\u00ebm t\u00eb treguesit. Analizimi dhe ekzekutimi i treguesit kryhet vet\u00ebm p\u00ebr shprehjet q\u00eb \u00e7ojn\u00eb n\u00eb ndryshimin e t\u00eb dh\u00ebnave. P\u00ebr m\u00eb tep\u00ebr, p\u00ebr t\u00eb reduktuar konsumimin e memories, n\u00eb vend t\u00eb alokimit statik t\u00eb bufereve p\u00ebr p\u00ebrpunimin e gabimeve n\u00eb tregues, \u00ebsht\u00eb realizuar kalimi n\u00eb alokimin dinamik t\u00eb memories sipas nevoj\u00ebs.\n
\u00cbsht\u00eb zgjeruar dalja e operacionit \u2018EXPLAIN\u2019, n\u00eb t\u00eb cilin tani shfaqen informacionet mbi p\u00ebrdorimin e leximit me shum\u00eb intervale (multi-range) dhe aplikimin e strategjis\u00eb s\u00eb gjysm\u00eb-bashkimit (semijoin), ku, gjat\u00eb operacioneve JOIN, p\u00ebrpunohen rreshtat vet\u00ebm nga nj\u00eb tavolin\u00eb.\n
Jan\u00eb garantuar ekzekutimet atomike t\u00eb operacioneve \u2018CREATE DATABASE\u2019 dhe \u2018DROP DATABASE\u2019 p\u00ebr t\u00eb mbrojtur nga d\u00ebshtimet n\u00eb rast t\u00eb mbylljes s\u00eb papritur ose t\u00eb gabimeve n\u00eb nivelin e sistemit t\u00eb skedar\u00ebve gjat\u00eb ekzekutimit t\u00eb k\u00ebtyre operacioneve. P\u00ebr shembull, m\u00eb par\u00eb, gjat\u00eb mbylljes s\u00eb papritur t\u00eb \u2018CREATE DATABASE\u2019, mund t\u00eb ishte formuar nj\u00eb struktur\u00eb e pap\u00ebrfunduar dhe e pakriptuar e depot t\u00eb DB-s\u00eb, p\u00ebr pastrimin e s\u00eb cil\u00ebs k\u00ebrkohej nd\u00ebrhyrje manuale.\n
N\u00eb procedurat e ruajtura t\u00eb shkruara n\u00eb JavaScript \u00ebsht\u00eb siguruar mb\u00ebshtetje p\u00ebr tipin VECTOR. T\u00eb dh\u00ebnat me k\u00ebt\u00eb tip tani mund t\u00eb kalohen n\u00eb parametrat e hyrjes dhe atyre t\u00eb kthimit.\n
\u00cbsht\u00eb shtuar mund\u00ebsia e autentifikimit gjat\u00eb lidhjes me DBMS duke p\u00ebrdorur protokollin OpenID Connect.\n
Jan\u00eb eliminuar 27 vulnerabilitete, nga t\u00eb cilat m\u00eb seriozja (CVE-2024-5535) ka marr\u00eb nivelin e rrezikut kritik (9.1 nga 10). Vulnerabiliteti mund t\u00eb shfryt\u00ebzohet n\u00eb m\u00ebnyr\u00eb t\u00eb larg\u00ebt pa kaluar autentifikimin. Problemi shkaktohet nga leximi i t\u00eb dh\u00ebnave nga nj\u00eb zon\u00eb jasht\u00eb tamponit t\u00eb alokuar n\u00eb bibliotek\u00ebn OpenSSL dhe rezulton n\u00eb p\u00ebrfundime t\u00eb papritura ose rrjedhje t\u00eb p\u00ebrmbajtjes s\u00eb memories n\u00eb p\u00ebrgjigjen pas lidhjes me serverin<\/a> me parametrat e gabuar t\u00eb protokollit. <\/ul>\n