readable and easy to edit:
https://mariadb.com/kb/en/library/with/
Best regards
Pantelis Theodosiou
On Thu, May 17, 2018 at 11:23 AM, wrote:
> You're not making a lot of sense here. Please explain the "ambiguity".
> That's a fairly complex query so you should include
B 10.1
<https://mariadb.com/kb/en/what-is-mariadb-101/>.
- The previous stable release is MariaDB 5.5
<https://mariadb.com/kb/en/what-is-mariadb-55/>.
Pantelis Theodosiou
___
Mailing list: https://launchpad.net/~maria-discuss
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 :)
>
> MySQL 8.0 has no CHECK
;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?
>>
>>
,
CONSTRAINT check_i_must_be_between_7_and_12
FOREIGN KEY (i_must_be_between_7_and_12)
REFERENCES truth (t)
);
On Wed, Apr 6, 2016 at 6:46 PM, Pantelis Theodosiou
wrote:
>
>
> On Mon, Apr 4, 2016 at 2:10 PM, Peter Laursen
> wrote:
>
>> As described in this Blog ht
On Mon, Apr 4, 2016 at 2:10 PM, Peter Laursen
wrote:
> As described in this Blog
> http://mablomy.blogspot.dk/2016/04/check-constraint-for-mysql-not-null-on.html.
> A very nice hack/trick IMO.
>
> However it is not working with MariaDB as VC's cannot be declared NOT
> NULL. What prevents that?
>
Did you mean to write
ORDER BY value ASC and ORDER BY value DESC
in the subqueries? The "ORDER BY date" doesn't make sense in the subqueries
as all the rows will have the same date, due to the "WHERE date=a.date"
correlation.
Pantelis
On Sat, Oct 3, 2015 at 2:12 AM, Roberto Spadim
wrote:
hanging version is 5.6.6 (not 5.5.7), at least in MySQL, and
- second, the values OFF / ON in the Maria documentation are reversed.
Apologies if this is not the correct list to raise the issue.
Pantelis Theodosiou
___
Mailing list: https://launchpad.ne
On Thu, Jun 12, 2014 at 9:57 AM, Federico Razzoli
wrote:
> Duplicate data cannot be inserted in MariaDB, in no cases.
>
> PostgreSQL has a different behaviour: transactions can optionally be
> "deferred", which means that integrity checks will be done on commit. This
> means that you can temporar
Roberto, Federico,
While I agree with your comments regarding use of ONLY_FULL_GROUP_BY, the
specific case has primary keys defined on (id), on both tables.
So, the GROUP BY t1.id has (or should have) no effect as every group will
have exactly one row and the results should be the deterministic.
Adam, you are right, bulk load project is 5835:
(2) InnoDB fast bulk load
Description: External tool to load CVS file directly to InnoDB file
space (innodb_file_per_table = 1).
https://mariadb.atlassian.net/browse/MDEV-5835
On Fri, Apr 11, 2014 at 5:28 PM, Adam Scott wrote:
> Second link i
Hello pslawek83,
as Sergei has already told you, the issue is not the uniqueness of the
indexes.
Some notes after reading your queries and the tables:
- I see two versions of the query, one having `attrib=5`, the other without.
- on table raw_stats_lookup, you do not have an index on (domain, id
12 matches
Mail list logo
