- discuss - lists.mariadb.org

Re: [Maria-discuss] mariadb-backup meta deb package
by Reindl Harald 14 Feb '18

14 Feb '18

Am 14.02.2018 um 12:56 schrieb Florent B: > On 14/02/2018 12:49, Sergei Golubchik wrote: >> Hi, Florent! >> >> On Feb 14, Florent B wrote: >>> Hi, >>> >>> Wouldn't be nice to have a metapackage mariadb-backup in Debian >>> repository, that depends on the current best version >>> (mariadb-backup-10.2, etc..) ? >>> >>> Like "mariadb-server" package in fact. >> Yes, I guess. >> It'll be consistent with what we do with the server. >> >> Of course, if you also have a solution how to reduce the number of >> packages, that'd be perfect :) >> >> Hmm, how about that? >> We rename the following packages to remove "-10.1" at the end. >> >> mariadb-connect-engine-10.1 >> mariadb-oqgraph-engine-10.1 >> mariadb-cracklib-password-check-10.1 >> mariadb-gssapi-server-10.1 >> mariadb-gssapi-client-10.1 >> mariadb-backup-10.1 >> >> This way the server package will specify the version (either >> "mariadb-server-10.1" for 10.1 or "mariadb-server" for the latest) >> and everything else will follow. >> >> Looks logical and doesn't increase the number of packages (!!!). >> But I need to try whether it'll actually work in Debian :) > > Wow ! Someone understood what I mean. Thank you a lot Sergei, I though I > was crazy seeing other people's answers well, i don't get why there needs to be a metapackage at all http://yum.mariadb.org/10.1/rhel6-x86/rpms/ http://yum.mariadb.org/10.2/rhel6-x86/rpms/ these are different repos and you have either 10.1 or 10.2 enabled whatever packages in whatever versions are there, the update manager without mention a version explicit takes the one with the highest number independent of a new install or update %package server Summary: The MariaDB server and related files Requires: %{name} = %{epoch}:%{version}-%{release}, %{name}-libs = %{epoch}:%{version}-%{release} Requires: sh-utils Requires(pre): shadow-utils Provides: mysql-server = %{epoch}:%{version}-%{release}, mysql-server%{?_isa} = %{epoch}:%{version}-%{release} Obsoletes: mysql-server, community-mysql-server %description server "dnf install mysql-server" == "dnf install mariadb-server" == "dnf install community-mysql-server" why? because the Provides/Obsoletes in my spec say so

1 0

Re: [Maria-discuss] mariadb-backup meta deb package
by Reindl Harald 14 Feb '18

14 Feb '18

Am 14.02.2018 um 10:51 schrieb Florent B: > Wouldn't be nice to have a metapackage mariadb-backup in Debian > repository, that depends on the current best version > (mariadb-backup-10.2, etc..) ? > > Like "mariadb-server" package in fact you missed to describe the problem you want to solve by step in with a solution which is always the wrong start because in case you didn't understand the real problem any solution is wrong

2 1

Re: [Maria-discuss] mariadb-backup meta deb package
by Sergei Golubchik 14 Feb '18

14 Feb '18

Hi, Florent! On Feb 14, Florent B wrote: > Hi, > > Wouldn't be nice to have a metapackage mariadb-backup in Debian > repository, that depends on the current best version > (mariadb-backup-10.2, etc..) ? > > Like "mariadb-server" package in fact. Yes, I guess. It'll be consistent with what we do with the server. Of course, if you also have a solution how to reduce the number of packages, that'd be perfect :) Hmm, how about that? We rename the following packages to remove "-10.1" at the end. mariadb-connect-engine-10.1 mariadb-oqgraph-engine-10.1 mariadb-cracklib-password-check-10.1 mariadb-gssapi-server-10.1 mariadb-gssapi-client-10.1 mariadb-backup-10.1 This way the server package will specify the version (either "mariadb-server-10.1" for 10.1 or "mariadb-server" for the latest) and everything else will follow. Looks logical and doesn't increase the number of packages (!!!). But I need to try whether it'll actually work in Debian :) Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org

1 0

Re: [Maria-discuss] mariadb-backup meta deb package
by Reindl Harald 14 Feb '18

14 Feb '18

Am 14.02.2018 um 12:22 schrieb Florent B: > I'm sorry but that's what not I mean. > > My message was just a suggestion, to have a "meta-package" for Debian > repository, like we have a meta-package "mariadb-server" that points to > "mariadb-server-10.2" (for example, if you installed 10.2 repository). > > In my deployment script, I just install "mariadb-server", without > specifying version. I would like to do the same for "mariadb-backup". > For now, I have to specify version of package : mariadb-backup-10.2. It > could be nice to have a "mariadb-backup" meta-package to point > automatically to the latest version available. stop talking about metapackages DAMNED! you mean "mariadb-backup" in it's last recent point-version should be in the 10.2 or 10.1 repository - why don't you say it then? don't get me wrong but it's hard when people fail to say what they mean and every response is a new riddle > On 14/02/2018 12:08, Vladislav Vaintroub wrote: >> >> The latest backup will not work with your 10.1 server. Mariabackup >> version should match server version that you have on the same box. >> >> mariabackup from 10.1 appears to work with 5.5 and 10.0, but this is >> merely by luck and by accident. >> >> *From: *Florent B <mailto:florent@coppint.com> >> *Sent: *Wednesday, February 14, 2018 11:58 AM >> *To: *maria-discuss(a)lists.launchpad.net >> <mailto:maria-discuss@lists.launchpad.net> >> *Subject: *Re: [Maria-discuss] mariadb-backup meta deb package >> >> On 14/02/2018 11:16, Reindl Harald wrote: >> >> > Am 14.02.2018 um 10:51 schrieb Florent B: >> >> >> Wouldn't be nice to have a metapackage mariadb-backup in Debian >> >> >> repository, that depends on the current best version >> >> >> (mariadb-backup-10.2, etc..) ? >> >> >> Like "mariadb-server" package in fact >> >> > you missed to describe the problem you want to solve by step in with a >> >> > solution which is always the wrong start because in case you didn't >> >> > understand the real problem any solution is wrong >> >> I just want to install the latest mariadb-backup package, without >> >> checking version by myself (10.1, 10.2...). >> >> Exactly the same as the "mariadb-server" metapackage for Debian, which >> >> points to latest version possible.

1 1

Re: [Maria-discuss] mariadb-backup meta deb package
by Federico Razzoli 14 Feb '18

14 Feb '18

I am not sure this is a good idea. Having a meta-package for the server and not one for mariabackup may seem inconsistent, but users are different. A lot of people just want MariaDB and don't (need to) care about versions. Maybe they barely know SQL and just want to run a simple script. For backups, it's different. If you need mariabackup you manage a MariaDB instance, and you need to care about versions. Federico Da: Florent B <florent(a)coppint.com> A: Vladislav Vaintroub <vvaintroub(a)gmail.com>; "maria-discuss(a)lists.launchpad.net" <maria-discuss(a)lists.launchpad.net> Inviato: Mercoledì 14 Febbraio 2018 12:23 Oggetto: Re: [Maria-discuss] mariadb-backup meta deb package I'm sorry but that's what not I mean. My message was just a suggestion, to have a "meta-package" for Debian repository, like we have a meta-package "mariadb-server" that points to "mariadb-server-10.2" (for example, if you installed 10.2 repository). In my deployment script, I just install "mariadb-server", without specifying version. I would like to do the same for "mariadb-backup". For now, I have to specify version of package : mariadb-backup-10.2. It could be nice to have a "mariadb-backup" meta-package to point automatically to the latest version available. On 14/02/2018 12:08, Vladislav Vaintroub wrote: #yiv8725764717 #yiv8725764717 -- _filtered #yiv8725764717 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv8725764717 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv8725764717 #yiv8725764717 p.yiv8725764717MsoNormal, #yiv8725764717 li.yiv8725764717MsoNormal, #yiv8725764717 div.yiv8725764717MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;}#yiv8725764717 a:link, #yiv8725764717 span.yiv8725764717MsoHyperlink {color:blue;text-decoration:underline;}#yiv8725764717 a:visited, #yiv8725764717 span.yiv8725764717MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv8725764717 .yiv8725764717MsoChpDefault {} _filtered #yiv8725764717 {margin:70.85pt 70.85pt 56.7pt 70.85pt;}#yiv8725764717 div.yiv8725764717WordSection1 {}#yiv8725764717 The latest backup will not work with your 10.1 server. Mariabackup version should match server version that you have on the same box. mariabackup from 10.1 appears to work with 5.5 and 10.0, but this is merely by luck and by accident. From: Florent B Sent: Wednesday, February 14, 2018 11:58 AM To: maria-discuss(a)lists.launchpad.net Subject: Re: [Maria-discuss] mariadb-backup meta deb package On 14/02/2018 11:16, Reindl Harald wrote: > > > Am 14.02.2018 um 10:51 schrieb Florent B: >> Wouldn't be nice to have a metapackage mariadb-backup in Debian >> repository, that depends on the current best version >> (mariadb-backup-10.2, etc..) ? >> >> Like "mariadb-server" package in fact > > you missed to describe the problem you want to solve by step in with a > solution which is always the wrong start because in case you didn't > understand the real problem any solution is wrong I just want to install the latest mariadb-backup package, without checking version by myself (10.1, 10.2...). Exactly the same as the "mariadb-server" metapackage for Debian, which points to latest version possible. _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

1 0

Re: [Maria-discuss] mariadb-backup meta deb package
by Reindl Harald 14 Feb '18

14 Feb '18

Am 14.02.2018 um 11:58 schrieb Florent B: > On 14/02/2018 11:16, Reindl Harald wrote: >> >> Am 14.02.2018 um 10:51 schrieb Florent B: >>> Wouldn't be nice to have a metapackage mariadb-backup in Debian >>> repository, that depends on the current best version >>> (mariadb-backup-10.2, etc..) ? >>> >>> Like "mariadb-server" package in fact >> >> you missed to describe the problem you want to solve by step in with a >> solution which is always the wrong start because in case you didn't >> understand the real problem any solution is wrong > > I just want to install the latest mariadb-backup package, without > checking version by myself (10.1, 10.2...). > Exactly the same as the "mariadb-server" metapackage for Debian, which > points to latest version possible besides that "mariadb-server" for sure is not a metapackage i doubt and hope for debian users that you don't get *major upgrade* and 10.1 to 10.2 *is* a major upgrade nobody upgrades just by the way you heavily confuse point updates and major upgrades 10.1 versus 10.2 is practically the same as 10 versus 11 just with different numbers but must not be confused with 10.1.10 to 10.1.11 and when you are at it learn what a meta-package is because in communication it's important to know what you are talking about https://askubuntu.com/questions/66257/what-is-the-difference-between-a-meta…

1 0

Re: [Maria-discuss] mariadb-backup meta deb package
by Vladislav Vaintroub 14 Feb '18

14 Feb '18

The latest backup will not work with your 10.1 server. Mariabackup version should match server version that you have on the same box. mariabackup from 10.1 appears to work with 5.5 and 10.0, but this is merely by luck and by accident. From: Florent B Sent: Wednesday, February 14, 2018 11:58 AM To: maria-discuss(a)lists.launchpad.net Subject: Re: [Maria-discuss] mariadb-backup meta deb package On 14/02/2018 11:16, Reindl Harald wrote: > > > Am 14.02.2018 um 10:51 schrieb Florent B: >> Wouldn't be nice to have a metapackage mariadb-backup in Debian >> repository, that depends on the current best version >> (mariadb-backup-10.2, etc..) ? >> >> Like "mariadb-server" package in fact > > you missed to describe the problem you want to solve by step in with a > solution which is always the wrong start because in case you didn't > understand the real problem any solution is wrong I just want to install the latest mariadb-backup package, without checking version by myself (10.1, 10.2...). Exactly the same as the "mariadb-server" metapackage for Debian, which points to latest version possible. _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

1 0

[Maria-discuss] [GSoC Idea Discussion] "mcsapi needs a new read API" project
by Udit Juneja 14 Feb '18

14 Feb '18

Hi, I am Udit Juneja, a Compter Science undergraduate student at Thapar Institute of Engineering and Technology, India. I am interested in contributing to MariaDB. A brief introduction about me: I am familiar with programming languages (C, C++, Python, PyCUDA, MySQL). I have won many hackathons. I am interested in "mcsapi needs a new read API" project. I have already started exploring MariaDB, and the APIs which are currently published on the website. I would like to discuss the idea further and maybe submit a proposal in GSoC later. Regards, Udit Juneja

3 2

[Maria-discuss] Google Summer of Code 2018 - MariaDB Foundation accepted
by Colin Charles 14 Feb '18

14 Feb '18

Hi, I just noticed this piece of good news — MariaDB Foundation is accepted to participate in the Google Summer of Code 2018 again — https://summerofcode.withgoogle.com/ There is an already healthy list of ideas: https://mariadb.com/kb/en/library/google-summer-of-code-2018/ Many already have mentors from MariaDB Corporation or MariaDB Foundation. Some are looking for mentors. Happy coding this summer! cheers, -colin -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

1 0

Re: [Maria-discuss] System versioned tables inquiry
by serg＠mariadb.org 12 Feb '18

12 Feb '18

Hi, Benjamin! First: please send questions like this to maria-discuss(a)lists.launchpad.net it's a public mailing list dedicated to MariaDB. I am subscribed, so I'll see you mail there, and you may be sure I will, because it won't be accidentally catched by my spam filter, or sorted out in some obscure folder. Furthermore other subscribers will see your question and could reply if I will be not available (e.g. I could be travelling). Thank you. On Feb 05, bartels.benjamin(a)tutanota.de wrote: > Hello Mr. Golubchik, > I have a couple of questions on MariaDB's implementation of the system > versioned tables if you are not busy. > 1. Is there any mechanism in the current implementation to insert rows > with custom values for ROW START and ROW END? I know that since they > are automatically implemented as auto generated columns that they are > not allowed to be modified. But I feel like this would make backup > migration very hard, since you cannot insert into these generated > columns. Maybe I am missing something but from what I can tell it is > not possible at the moment.MSSQL from my understanding doesn't > restrict the ROW START and ROW END columns to generated columns so it > is possible to insert some data into those columns and then alter the > table to make it system versioned.See (Listing > 1): http://www.itprotoday.com/microsoft-sql-server/first-look-system-versioned-… No, there is none. It is intentional, to protect the integrity of the history. SQL Standard, as far as I know, does not provide any way of falsifying the history of system versioned tables. There is another feature in the standard: application-time period tables, in there one can provide arbitrary values for start and end timestamps. But MariaDB 10.3 doesn't support application-time period tables. As for backups, yes, I agree, it's a problem. Binary backups will preserve the history just fine, but mysqldump backups will not, they'll reset the history. > 2. What is supposed to be done in 2038 when NOW() will surpass the ROW > END column? Will there be a way to have a bigger underlying datatype > to represent the historic columns? That's the common issue for any TIMESTAMP columns. We don't have any solution specific to system versioned tables. I could *guess* that closer to that date TIMESTAMP width will be increased and, perhaps, there will be some migration procedure in mysql_uprade. There are no specific plans yet. Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org

1 0