Re: [Maria-discuss] The future of Dynamic Columns

Hi I agree that EAV is a pain in the ass. Having several very similar tables that represent flavors of the same "parent entity" is a pain too. Dynamic Columns are logically simple. I think that the problem is that people don't really know them. And if one tries to explore them, he finds a synt

Re: [Maria-discuss] The future of Dynamic Columns

yeap, i agree in my opnion... today without "expression index" to allow a faster search (on attribute or value) it's not possible to only use dynamic columns cause we get full table scan, today a second table with attribute-value should be necessary in this case to have a better performace what we

Re: [Maria-discuss] The future of Dynamic Columns

Just wanted to add, any application that wants to store forms data without having to create a new table every time you create a new form could benefit from dynamic columns. In the database design world, any design that is of the EAV (Entity-Attribute-Value) style would benefit from dynamic columns

Re: [Maria-discuss] The future of Dynamic Columns

Hi, Tom! On 29.01.15 01:12, Tom Worster wrote: [skip] And Maria promises us that we could use that expression to write the value back and the result will be the exact same thing. A sort of idempotency promise (kinda). This doesn't make the interface any less clunky (on the contrary) but I hav

Re: [Maria-discuss] The future of Dynamic Columns

On 1/28/15, 5:41 PM, "Oleksandr Byelkin" wrote: >Hi, Tom! > >On 28.01.15 23:01, Tom Worster wrote: >> While functions for getting and setting via json might be useful, I >> think they are peripheral to the core datatype problem here. >> >> The interface to dynamic columns in Maria is SQL. The in

[Maria-discuss] Fwd: Re: The future of Dynamic Columns

Hi! Sorry I forgot to put in in the list. Forwarded Message Тема: Re: [Maria-discuss] The future of Dynamic Columns Дата: Wed, 28 Jan 2015 23:44:39 +0100 Від:Oleksandr Byelkin Кому: Roberto Spadim Hi, Roberto! On 28.01.15 23:13, Roberto Spadim wrote: Hi Peter :

Re: [Maria-discuss] The future of Dynamic Columns

Hi, Tom! On 28.01.15 23:01, Tom Worster wrote: While functions for getting and setting via json might be useful, I think they are peripheral to the core datatype problem here. The interface to dynamic columns in Maria is SQL. The internal datatypes are SQLish. We can be completely sure of wh

Re: [Maria-discuss] The future of Dynamic Columns

Hi Peter :) i will talk about what i used and what i consider interesting to have, 2015-01-28 19:25 GMT-02:00 Peter Laursen : > @Roberto. A comment to "i think it's a nice human readable format for > arrays/objects, nothing less nothing more". > > But why will you then need to **store** as JSON

Re: [Maria-discuss] The future of Dynamic Columns

While functions for getting and setting via json might be useful, I think they are peripheral to the core datatype problem here. The interface to dynamic columns in Maria is SQL. The internal datatypes are SQLish. We can be completely sure of what was set, in SQL terms, by a COLUMN_CREATE(). But

Re: [Maria-discuss] The future of Dynamic Columns

@Roberto. A comment to "i think it's a nice human readable format for arrays/objects, nothing less nothing more". But why will you then need to **store** as JSON? Could not something like "SELECT .. INTO JSON ..." do the trick? (with hindsight: "SELECT .. INTO XML ..." could have been implemented

Re: [Maria-discuss] The future of Dynamic Columns

i think a good start is "expression index​es" and after json syntax to SQL language, and some new functions to handle json/etc CREATE INDEX name ON table ( some_function(field) ) maybe dynamic column functions, or json functions? or any function deterministic (for example, NOW() function can't

Re: [Maria-discuss] The future of Dynamic Columns

Hi Sergei, Your reply complements Oleksandr's and is welcome. Your remarks about tepid user response to Dynamic Columns makes me want to reiterate the comments about better marketing my reply to Oleksandr. But you make even more clear that the flip side is very important. Users need to show their

Re: [Maria-discuss] The future of Dynamic Columns

Hi, Tom! On 28.01.15 18:04, Tom Worster wrote: Hi Oleksandr, Thank you for the response. It helps me make my decision by narrowing the options. I cannot help with money. My company doesn't have any (really! our market is non-commercial radio stations) but if the ORM extension turns out well th

Re: [Maria-discuss] The future of Dynamic Columns

Hi Oleksandr, Thank you for the response. It helps me make my decision by narrowing the options. I cannot help with money. My company doesn't have any (really! our market is non-commercial radio stations) but if the ORM extension turns out well then perhaps it helps some more people to use MDC.

Re: [Maria-discuss] The future of Dynamic Columns

some points 2015-01-28 14:06 GMT-02:00 Peter Laursen : > This discussion reminds me of 6-8 years back when XML was introduced in > MySQL ("LOAD DATA XML, "mysqldump --xml", XML functions (ExtractValue > etc.). It was a *big hype* at the time it was introduced. Now it seems to > be an almost forg

Re: [Maria-discuss] The future of Dynamic Columns

This discussion reminds me of 6-8 years back when XML was introduced in MySQL ("LOAD DATA XML, "mysqldump --xml", XML functions (ExtractValue etc.). It was a *big hype* at the time it was introduced. Now it seems to be an almost forgotten feature used by close_to_nobody. What should a JSON option

Re: [Maria-discuss] The future of Dynamic Columns

i will give some ideas , some could be stupid but that's just ideas... 1)could be nice a json language as data results, for example SELECT {'some array':'some value',column1:column2} AS column1 FROM some_table the result of {} is a string utf8, but well know as json format, the sql server just in

Re: [Maria-discuss] The future of Dynamic Columns

Hi, Tom! On Jan 27, Tom Worster wrote: > 2. In at least two places (one was here > ) > I've read text with the implied meaning, "we may improve such-and-such > about MDC if and when people start actually using it." While

Re: [Maria-discuss] MariaDB 10.0.16 now available

On Wed, Jan 28, 2015 at 9:39 AM, Peter Laursen wrote: > YaST "Online Update" interface did not (both yesterday and two hours ago), > does not and will not identify that there is an upgrade available for > MariaDB 10.0.15, when there actually was/is. I cannot decide it this is an > issue with the R

Re: [Maria-discuss] MariaDB 10.0.16 now available

Discussion of mirrors is irrelevant for what I experienced. This is clear now. YaST "Online Update" interface did not (both yesterday and two hours ago), does not and will not identify that there is an upgrade available for MariaDB 10.0.15, when there actually was/is. I cannot decide it this is an

Re: [Maria-discuss] MariaDB 10.0.16 now available

Am 28.01.2015 um 15:23 schrieb Peter Laursen: When downloadingg/upgrading packagaes from inside SuSE/YaST you on't specify a mirror. There is no such option. SuSE handles this (it probably tries all mirrors till it finds one that works). it just takes a *random* mirror from the mirror list to

Re: [Maria-discuss] MariaDB 10.0.16 now available

When downloadingg/upgrading packagaes from inside SuSE/YaST you on't specify a mirror. There is no such option. SuSE handles this (it probably tries all mirrors till it finds one that works). The problem is and was that MariaDB 10.0.16 does not identify itself as an upgrade for 10.0.15 in a way th

Re: [Maria-discuss] MariaDB 10.0.16 now available

Hi, On 28 Jan 2015, at 04:06, Peter Laursen wrote: > I did not learn anything and obvuously you did not either. We have agreed > before that you will not comment on my posts to MariaDB mailing lists. I also > ignore yours. PERIOD! > Can we please act maturely on a public mailing list? > A

Re: [Maria-discuss] MariaDB 10.0.16 now available

On theOpenSuSE 'Tumbleweed' distro "sudo zypper dup" did fetch and install MariaDB 10..0.16 -- Peter On Wed, Jan 28, 2015 at 1:09 PM, Peter Laursen wrote: > ... it will tell me that .is installed and 1.0.16 is availoble > > >> > > ... it will tell me that 10.0.15 is installed and 10.0.16 is av

Re: [Maria-discuss] Unable to DROP table, Data Dict problem

Hi Jan, the root cause for the corruption, we know: NFSv4 bugs. The "dump/restore-to-new-db" path we know as well. My question here is: is there a way to get rid of this table _without restoring to a new DB_. thanks, martin On Wed, Jan 28, 2015 at 2:05 AM, Jan Lindström wrote: > Hi, > > Yes

Re: [Maria-discuss] MariaDB 10.0.16 now available

... it will tell me that .is installed and 1.0.16 is availoble >> ... it will tell me that 10.0.15 is installed and 10.0.16 is available On Wed, Jan 28, 2015 at 1:06 PM, Peter Laursen wrote: > The problem was/is another. The packages are available (now they are at > least) . But they are not

Re: [Maria-discuss] MariaDB 10.0.16 now available

The problem was/is another. The packages are available (now they are at least) . But they are not listed in in YaST "Online Update" interface. However if I go to "Software Management" interface and search "mariadb" it will tell me that .is installed and 1.0.16 is availoble. 10.0.16 is installed i