On 15/10/16 03:33, Jon Foster wrote:
> I have a DB scenario that is very write intensive. Essentially its a
> large scale hit counter of sorts. Currently we're running on a single
> 12core server with 6 SSDs in a RAID6 array.
Not using RAID6 would be a good start.
> But we're looking for a way
On 16/10/16 09:26, Alex Evonosky wrote:
> Hello team-
>
> Quick question-
>
> I recently just installed mariaDB 10.1.18 (via apt-get) and all went
> well, no issues.. Here is my galera.cnf file:
>
> cat galera.cnf
> [mysqld]
> binlog_format = ROW
> default_storage_engine
On Sun, Oct 16, 2016 at 5:15 PM, Sergei Golubchik wrote:
> Hi, Peter!
>
> On Oct 16, Peter Laursen wrote:
> > Didn't CHECK CONSTRAINTS get introduced in MySQL 8? Then better port it
> > from there into MariaDB I think. -- Peter
>
> I'm afraid you've got it backwards :)
>
>
As Sergei said, MariaDB 10.2 has CHECKs.
In old versions, honestly I don't like your solution. Take a look at what locks
will be set:
https://www.percona.com/blog/2006/12/12/innodb-locking-and-foreign-keys/
You can use trigger instead. When you only want to execute a check like this,
triggers
I was a software developer at Tokutek working on TokuDB. If I wanted to
continue working on TokuDB, Tokutek had to make money to pay for the
expenses of running a company. Supporting TokuDB on Windows led to
absolutely no business, so why would I want to waste time supporting it?
We would jump
ok .. I should have checked properly! :-(
On Sun, Oct 16, 2016 at 6:15 PM, Sergei Golubchik wrote:
> Hi, Peter!
>
> On Oct 16, Peter Laursen wrote:
> > Didn't CHECK CONSTRAINTS get introduced in MySQL 8? Then better port it
> > from there into MariaDB I think. -- Peter
>
>
Hi, Peter!
On Oct 16, Peter Laursen wrote:
> Didn't CHECK CONSTRAINTS get introduced in MySQL 8? Then better port it
> from there into MariaDB I think. -- Peter
I'm afraid you've got it backwards :)
MySQL 8.0 has no CHECK constraint (at least it's not mentioned in
My suggestion is for documenting existing functionality and a use case for
VIRTUAL columns.
When CHECK constraints are actually added, it will be obsolete of course
but still useful for those that use older versions (5, 10).
On Sun, Oct 16, 2016 at 3:51 PM, Peter Laursen
Didn't CHECK CONSTRAINTS get introduced in MySQL 8? Then better port it
from there into MariaDB I think. -- Peter
On Sun, Oct 16, 2016 at 4:45 PM, Pantelis Theodosiou
wrote:
> Would this be good to be added in the documentation of VIRTUAL columns?
>
> Or as a separate page,
But those people can't use Galera, pt, Xtrabackup... If we care about Windows,
that software should be ported first, because it's general purpose.
Federico
Dom 16/10/16, Tim Callaghan ha scritto:
Oggetto: Re:
Doesn't the Bing team port rocks? Obviously there is interest in support for
Windows in Redmond, but apparently not for TokuDB.
The market decides. It has been demonstrated that TokuDB isn't precisely
general purpose, so the desire to port it is lesser.
Plenty of people run Windows and MySQL
I was just adding context. I agree that Windows is very uninteresting in a
production context, but not having a version of TokuDB for Windows
certainly excluded people (academic and professional) from trying it out on
their laptops.
On Sat, Oct 15, 2016 at 1:10 PM, Reindl Harald
Hi!
Visiting:
https://mariadb.com/kb/en/mariadb/branding-guidelines/
You’ll note that the Powered by MariaDB badges still exist
(https://mariadb.org/about/logos/) — they should really say Powered by MariaDB
Server
But what is missing are all the seal logos? Currently beyond the
could you get rid of
* top posting
* convert a plaintext thread to html
* reply all?
Am 16.10.2016 um 04:09 schrieb Roberto Spadim:
There're financial software running windows withoutproblems
that is all nice - but the whole point of a database server which is
reachable over network is that
14 matches
Mail list logo