- docs - lists.mariadb.org

[Maria-docs] GA should also mean "documented" :)
by Federico Razzoli 23 May '17

23 May '17

It's great to see that 10.2 is now GA. But from a quick look, I've seen that documentation is incomplete: * Recursive CTE not documented: https://mariadb.com/kb/en/mariadb/common-table-expressions/ * Window functions: "this article is currently incomplete" https://mariadb.com/kb/en/mariadb/window-functions-overview/ There could be other undocumented features, these are the ones I've found immediately. Please, fill those gaps so we can test the features. Regards, Federico

2 1

[Maria-docs] Fwd: mysql_secure_installation documentation
by Michal Schorm 20 Dec '16

20 Dec '16

Hello all, I took care about bug against "mysql_secure_installation" script. [1] The problem is pretty simple. When you use "mysql_secure_installation" script, it will ingore all of yours current configuration. However, there are some options, that can be used. One of them is used to add your custom config file. It is documented, for example, here: [2] Unfortunatelly, the "man mysql_secure_installation" is quite short of infromation. (same as [3]) I believe, the information about options really should be added to both manpage and [3]. That should also solve the bug, without any [1] https://bugzilla.redhat.com/show_bug.cgi?id=1260821 [2] https://dev.mysql.com/doc/refman/5.7/en/mysql-secure-installation.html [3] https://mariadb.com/kb/en/mariadb/mysql_secure_installation/ -- I would like your general opinion about this. Based on it, I can file issue on JIRA. -- Michal Schorm Core Services - Databases Team mail: mschorm(a)redhat.com Brno-IRC: mschorm

1 0

Re: [Maria-docs] undocumented features?
by Federico Razzoli 22 Aug '16

22 Aug '16

Hi Ian Please don't take this as an accuse. I understand that keeping documentation and links updated requires a great effort. Generally you are doing a great work, and it wouldn't be reasonable to expect a flawless documentation. But I still think that I found an undocumented feature. You confirm that probably there are other cases, and I think this is a problem that should be fixed somehow. Let me explain better my point of view. A statement documentation page is expected to include the complete syntax, so if I look at GRANT page and don't find a privilege, that privilege doesn't exist for me. Mentioning the feature in another page, and without any details, is not enough. Also note that HELP has the same problem. I think that most users don't know that HELP contents refer to MySQL (and the KB lacks this info). In my opinion, if you cannot fill the help tables with MariaDB-specific information, you should return a warning every time a user runs HELP command. Bye, Federico -------------------------------------------- Gio 11/8/16, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: Re: [Maria-docs] undocumented features? A: maria-docs(a)lists.launchpad.net Data: Giovedì 11 agosto 2016, 17:10 Hi Federico I know one of the weaknesses has been adding new content as a new article, and then not cross-linking it on all related pages, so you're right that this is probably not the only case. It'll be quite hard to 'check that all ... features are documented in the proper KB page' though! If I do spot anything will be sure to add it, otherwise feel free to add/report if you spot something. Thanks for adding the missing content in this case. On 11/08/2016 10:36, Federico Razzoli wrote: > Hi all! > > I have a request: could you please check that all current/future features are documented in the proper KB page? The request includes "sub-features", that is, syntaxes that were implemented as part of a more generic feature. It is very possible that there are undocumented things, in my opinion. > > For example, I just documented GRANT ... MAX_STATENENT_TIME. I learned it exists because I've read this page: > https://mariadb.com/kb/en/mariadb/aborting-statements/ > > However the GRANT page didn't mention that syntax until I added that content. This means that, even if a user reads the documentation, he hardly knows about this feature. Also, I needed to experiment: in fact, from the above page, it wasn't clear if MAX_STATEMENT_TIME was a permission or a user resourse limit. > > Again, this is just a request, not criticism. I'm writing this mail because, in my opinion, we all would benefit from all features being documented. > > Thank you for your great work, MariaDB! > > Regards > Federico _______________________________________________ Mailing list: https://launchpad.net/~maria-docs Post to : maria-docs(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-docs More help : https://help.launchpad.net/ListHelp

2 1

[Maria-docs] undocumented features?
by Federico Razzoli 11 Aug '16

11 Aug '16

Hi all! I have a request: could you please check that all current/future features are documented in the proper KB page? The request includes "sub-features", that is, syntaxes that were implemented as part of a more generic feature. It is very possible that there are undocumented things, in my opinion. For example, I just documented GRANT ... MAX_STATENENT_TIME. I learned it exists because I've read this page: https://mariadb.com/kb/en/mariadb/aborting-statements/ However the GRANT page didn't mention that syntax until I added that content. This means that, even if a user reads the documentation, he hardly knows about this feature. Also, I needed to experiment: in fact, from the above page, it wasn't clear if MAX_STATEMENT_TIME was a permission or a user resourse limit. Again, this is just a request, not criticism. I'm writing this mail because, in my opinion, we all would benefit from all features being documented. Thank you for your great work, MariaDB! Regards Federico

2 1

[Maria-docs] Is there a way to see release specific docs for spatial support?
by Michael Moore 01 Jun '16

01 Jun '16

Hi, I'm trying to put together a table of which spatial functions are supported by MySQL and MariaDB at which version numbers. Something like https://dev.mysql.com/doc/refman/5.5/en/spatial-function-reference.html for different versions would be awesome, but I can't find it. Checking wiki history isn't very helpful because it just shows a date that it was changed, with no mention of why. Is there a better approach I could be taking? I'm making the table for WordPress plugin developers, who have to deal with sometimes old versions of MySQL and MariaDB on their hosts without control over the upgrade schedule. Once I have the table compiled I'd love to share it back on the MariaDB KB for future people looking for the same thing. Many thanks, Michael Moore

2 10

[Maria-docs] New mariadb.org in the works
by Otto Kekäläinen 18 Dec '15

18 Dec '15

Hello! We are about to renew the mariadb.org website. The idea is to replace the current mariadb.org and blog.mariadb.org with one single site that includes both the basic information about the software project and the MariaDB Foundation, as well as the blog. Work in progress is visible at https://new.mariadb.org/ Please send us your feedback!

1 1

Re: [Maria-docs] [Maria-discuss] Moving from Launchpad lists to something else... ?
by Tom Worster 19 Oct '15

19 Oct '15

On 10/15/15, 5:03 AM, "Maria-discuss on behalf of Colin Charles" <maria-discuss-bounces+fsb=thefsb.org(a)lists.launchpad.net on behalf of colin(a)mariadb.org> wrote: >> On 15 Oct 2015, at 05:35, Jean Weisbuch <jean(a)phpnet.org> wrote: >> >> To be able to give the best answer we must first know what is >>motivating the move from LP. > >So the reason we were thinking of ditching launchpad for mailing lists: >1. When there was a MariaDB-Manager google group, that group got a lot of >user posts about MariaDB Server. That group now no longer exists, but it >gave us a hint that people are interested in a Google group > >2. We moved everything from Launchpad (bugs to Jira, code to Github) and >the only thing remaining is mailing lists > >3. The MariaDB Knowledgebase: https://mariadb.com/kb/en/ used to have an >OpenID login that would be useful if you had a LP account, but OpenID is >apparently going away (or gone), so there’s less use for LP > >4. LaunchPad itself seems to be “hard” for people to signup (see #1). Good points. Making it easy for people to get involved is important, but if that's the idea then moving to Google Groups isn't a great solution. Apart from it being old and clunky owing to Google's neglect, the insurmountable problem is that it's still an email list at core. Personally, I like email lists best but I'm very old and have been in computing since the 70s, and I accept that most of the rest of the world has moved on. Another problem the Maria community might consider together with the discuss email list is the low quality and participation in the web Q&A of the Knowledge Base. That sometimes makes me sad. There is now a decent open-source system that can function as email list replacement and provide web and mobile Q&A, as well as other stuff: https://www.discourse.org I've used it at New Relic and it seems pretty good. It's got a lot of good stuff and I want to highlight just two. 1. "Mailing List Support - Opt into a special mode where all messages are sent to you via email, exactly like a mailing list. Start new topics via email." 2. You can host it yourself or pay someone you trust to do so. It's not a "free" cloud service where you pay by feeding the internet advertising/surveillance economy. I don't know if Discourse is right for Maria but I wouldn't mention it if I didn't think it might help build a bigger and more active support community, which I long for. Tom

2 1

[Maria-docs] Moving from Launchpad lists to something else... ?
by Colin Charles 14 Oct '15

14 Oct '15

Hi, I was speaking to Otto (CEO, MariaDB Foundation) and discussing that we should move the lists from Launchpad to something else. We obviously want to preserve the archives, and this isn’t going to happen overnight (something like an aim by the end of the year). Would you be ok with running on Google Groups? Would you prefer being on Mailman? Do you have another self-hosted or (preferably free) hosted solution as your preference? Today, we have several lists (maria-discuss, maria-developers, maria-docs) that are hosted on Launchpad. We also have a few lists (ambassadors, announce, commits, mirroring, maria-buildbot-reports) hosted on Mailman at lists.askmonty.org. Let us know what you think about this Kind Regards, Colin Charles -- Colin Charles, Chief Evangelist, MariaDB Corporation blog: http://bytebot.net/blog/ | t: +1-347-903-3201 | Skype: colincharles | Twitter: @bytebot

2 1

[Maria-docs] TOC link doesn't work if a heading doesn't include ASCII alphanumerics
by 100の人 20 Jul '15

20 Jul '15

Hello, A link in a table of contents generated by <<toc>> macro doesn't work if its corresponding heading doesn't include ASCII alphanumerics. The reason is that characters that can not be converted into ASCII alphanumerics are treated as spaces in headings. If a heading only includes the characters, its "id" attribute is an empty string. For example, this page: https://mariadb.com/kb/zh-cn/getting-started-with-indexes/ As of now, a editor need to append an extra <<style>> macro to avoid the dead link. For example: "== 第一章 <<style style="content: 'Heading One';">> <</style>>" (https://mariadb.com/kb/ja/toc/) I think a possible solution would be to treat some non-ASCII characters as ASCII alphanumerics. For example, "== 第一章" would be converted to "<h2 id="第一章">第一章</h2>". The character probably can be expressed by this regular expression: /[\p{Cyrillic}\p{Han}\p{Hangul}\p{Hiragana}\p{Katakana}]/ Thanks, -- 100の人

3 3

[Maria-docs] improving docs around show slave status
by Colin Charles 18 Jun '15

18 Jun '15

hi, just noted this from irc, we don't have detailed docs around things like seconds_behind_master, etc. compare https://mariadb.com/kb/en/mariadb/show-slave-status/ vs http://dev.mysql.com/doc/refman/5.6/en/show-slave-status.html It might be better than us having to look at the code from time to time cheers, -colin -- Colin Charles, Chief Evangelist, MariaDB Corporation blog: http://bytebot.net/blog/| t: +6-012-204-3201 | Skype: colincharles

3 4