Hello,
A new question has been asked in "Client Libraries" by tommy_pham_g. Please
answer it at
http://mariadb.com/kb/en/resultsetmetadata-getcolumnclassname-accuracy-for-jdbc/
as the person asking the question may not be subscribed to the mailing list.
Hi folk
At least 10.1.3 does not suffer from this defect. :-)
-- Peter
On Mon, Mar 2, 2015 at 4:31 PM, Peter Laursen
wrote:
> The 10.0.17 announcement just arrived to my mailbox. Did you fix the
> problem with service being destroyed in the build I downloaded 2 days ago?
>
> -- Peter
>
> On Sat, Feb 28
Actually I think the behavior of MariaDB here is somewhat consistent with
how MySQL always did - see
CREATE TABLE blah (id INT) ENGINE = MYISAM MAX_ROWS = 500;
ALTER TABLE blah ENGINE = INNODB;
SHOW CREATE TABLE blah;
/*
CREATE TABLE `blah` (
`id` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHA
The 10.0.17 announcement just arrived to my mailbox. Did you fix the
problem with service being destroyed in the build I downloaded 2 days ago?
-- Peter
On Sat, Feb 28, 2015 at 11:31 AM, Peter Laursen
wrote:
> Problem seems to persist in 10.0.17. Service is not created. :-(
>
> -- Peter
>
> On
The MariaDB project is pleased to announce the immediate availability
of MariaDB 10.0.17 & 10.1.3
MariaDB 10.0.17 is a Stable (GA) release. MariaDB 10.1.3 is a Beta
release. See the Release Notes and Changelog for details.
- - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
At least the error/warning message is wrong IMO.
>> this
Table storage engine 'InnoDB' does not support the create option
'TRANSACTIONAL=1'
>> should rather be something like
Table storage engine 'InnoDB' does not support the create option
'TRANSACTIONAL'. We preserve it though so that ALTER opera
On 02/03/2015 15:37, Reindl Harald wrote:
Am 02.03.2015 um 14:26 schrieb Ian Gilfillan:
This is probably because strict mode is set. If unset, it should return
a warning, not an error. From MariaDB 10.1.2, you can use:
SET STATEMENT sql_mode='' FOR ALTER TABLE `systemevents` ENGINE =
InnoDB;
Just as a side note, its possible to remove the TRANSACTIONAL=x option
by adding TRANSACTIONAL=default on the ALTER statement.
A similar issue arises if for example ROW_FORMAT=PAGE is used on the
ARIA table as it doesnt exists on InnoDB, it will issue a warning
"InnoDB: assuming ROW_FORMAT=COM
Thanks to Jean. Even this works:
CREATE TABLE `systemevents` (
`ID` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
`DeviceReportedTime` DATETIME DEFAULT NULL,
`FromHost` VARCHAR(30) CHARACTER SET latin1 COLLATE latin1_german1_ci NOT
NULL,
`Message` TEXT,
`SysLogTag` VARCHAR(60) DEFAULT NULL,
Hi, Reindl!
On Mar 02, Reindl Harald wrote:
> how do someone convert a Aria table to another engine?
> MyISAM and InnoDB results in the same error
> ___
>
> MariaDB [dbmail]> ALTER TABLE `systemevents` ENGINE = InnoDB;
> ERROR 1478 (HY000):
Am 02.03.2015 um 15:22 schrieb Jean Weisbuch:
Just as a side note, its possible to remove the TRANSACTIONAL=x option
by adding TRANSACTIONAL=default on the ALTER statement.
wouldn't a "ALTER TABLE `systemevents` ENGINE=InnoDB DEFAULTS;" be more
logical which should be default in case of stri
Am 02.03.2015 um 15:03 schrieb Ian Gilfillan:
On 02/03/2015 15:37, Reindl Harald wrote:
Am 02.03.2015 um 14:26 schrieb Ian Gilfillan:
This is probably because strict mode is set. If unset, it should return
a warning, not an error. From MariaDB 10.1.2, you can use:
SET STATEMENT sql_mode='' F
I agree with Harald here!
-- Peter
On Mon, Mar 2, 2015 at 2:37 PM, Reindl Harald
wrote:
>
> Am 02.03.2015 um 14:26 schrieb Ian Gilfillan:
>
>> This is probably because strict mode is set. If unset, it should return
>> a warning, not an error. From MariaDB 10.1.2, you can use:
>> SET STATEMENT s
Am 02.03.2015 um 14:26 schrieb Ian Gilfillan:
This is probably because strict mode is set. If unset, it should return
a warning, not an error. From MariaDB 10.1.2, you can use:
SET STATEMENT sql_mode='' FOR ALTER TABLE `systemevents` ENGINE = InnoDB;
which will unset strict mode just for that qu
This is probably because strict mode is set. If unset, it should return
a warning, not an error. From MariaDB 10.1.2, you can use:
SET STATEMENT sql_mode='' FOR ALTER TABLE `systemevents` ENGINE = InnoDB;
which will unset strict mode just for that query, otherwise for older
versions just set it
how do someone convert a Aria table to another engine?
MyISAM and InnoDB results in the same error
___
MariaDB [dbmail]> ALTER TABLE `systemevents` ENGINE = InnoDB;
ERROR 1478 (HY000): Table storage engine 'InnoDB' does not support the
crea
Hi, Tom!
On Mar 01, Tom Worster wrote:
> so it turns out the problem is my incompetence. i thought blob allowed
> long values.
>
> i've been using mysql since 3.something and i still don't know much
> about its abundance of types.
>
> i retract my comments and crawl back into my hole.
In fact,
17 matches
Mail list logo
