All right I will think about it, for mariadb if you remember I wrote you that the problem was clear, so I can do some code modification to permit the usage of mariadb.
About that, I would like to ask you an hint in using git and working with oak, as I said I have not much experience in working in opensource projects and git sometimes is so hard to understand, so consider my current scenariio: * I have my fork of oak where I did commit for the mongodb driver upgrade * Then I branched it to do the other bugfix you asked me * Now, my pull request about mongodb upgrade is still pending and ok (this is another topic but I really would like that pull request can go on, if i can help tell me) * if I want to work to new issue, for example this one about mariadb, how should I work? Should I delete my fork and forking again main oak trunk or this is wrong and risk losing data? Could I align my fork with latest commit but I don't know how and start working with the new issue in that fork? Should I branch again my fork but in this way it still remains some commits behind? I have so many doubts 🙂 ... Thanks, bye Cordiali saluti / Best regards, Raffaele Gambelli Senior Java Developer E [email protected]<mailto:[email protected]> [CEGEKA] Via Ettore Cristoni, 84 IT-40033 Bologna (IT),Italy T +39 02 2544271 WWW.CEGEKA.COM<https://www.cegeka.com/> [https://signature.cegeka.com/SignatureRO/bannerRO.jpg] ________________________________ From: Julian Reschke <[email protected]> Sent: Wednesday, October 9, 2024 8:39 AM To: [email protected] <[email protected]> Subject: Re: Problems in using RDB DocumentStore on mariadb On 30.09.2024 09:03, Raffaele Gambelli wrote: > In RDBDocumentStoreDB: > > public String getTableCreationStatement(String tableName, int schema) { > return "create table " + tableName > + " (ID varchar(512) not null primary key, MODIFIED bigint, > HASBINARY smallint, DELETEDONCE smallint, MODCOUNT bigint, CMODCOUNT bigint, > DSIZE bigint, " > + (schema >= 1 ? "VERSION smallint, " : "") > + (schema >= 2 ? "SDTYPE smallint, SDMAXREVTIME bigint, " : > "") > + "DATA varchar(16384), BDATA blob(" + 1024 * 1024 * 1024 + > "))"; > > But using utf8mb4 that DATA becomes 16384 * 4 = 65536, in mariadb the varchar > max is 65,532. The effective maximum length of a VARCHAR is subject to the > maximum row size and the character set used > > MySql behaves the same so I can't understand the suggestion in using utf8mb4 > given that create table statement, could you explain please? > > Thanks Raffaele, if you're still interested in this, and if you're familiar with Docker, it would be helpful if you can document how to run either Mariadb or Mysql inside Docker, and document it in https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fjackrabbit-oak%2Fblob%2Ftrunk%2Foak-doc%2Fsrc%2Fsite%2Fmarkdown%2Ftesting.md&data=05%7C02%7CRaffaele.Gambelli%40cegeka.com%7C8c462f9096564c4af0c508dce82d3dd1%7C42151053019347aa9e81effd81f772cc%7C0%7C0%7C638640528219301864%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=DUMdktF6SiFdCnd1DYw3ql8V9LDLzlMXYEltX6guYkw%3D&reserved=0<https://github.com/apache/jackrabbit-oak/blob/trunk/oak-doc/src/site/markdown/testing.md> Best regards, Julian
