MySQL doesn't work at all

Thread is closed for posting
5 posts, 0 answers
  1. Dmitry Semenov
    Dmitry Semenov avatar
    1 posts
    Member since:
    Jan 2010

    Posted 08 Jun 2010 Link to this post

    MySQL 5.1.47
    MySQL connector/net 6.3.2

    that's what I get:

    any ideas?

  2. Alexander
    Alexander avatar
    727 posts

    Posted 09 Jun 2010 Link to this post

    Hello Dmitry Semenov,

    Unfortunately I was not able to reproduce the error although I am testing with the same versions of Visual Studio, OpenAccess, MySql and MySql connector. Could you please share with us how the connection string that you are trying to use looks like? Hopefully we will be able to see where the problem could be.

    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  3. gmendez
    gmendez avatar
    82 posts
    Member since:
    Jun 2012

    Posted 19 Jan 2011 Link to this post

    Hello, I have found an issue regarding MySql 5.5 which I think is a bug.
    I have a simple class, and when trying to perform forward mapping I get the following error:

    Error 1 OpenAccess Error: Telerik.OpenAccess: Updating SQL schema failed. Telerik.OpenAccess.OpenAccessException: SQL exception on 'CREATE TABLE `tronco` ( `tronco_id` INTEGER NOT NULL,  `codigo` VARCHAR(255) NULL,  `diametro` INTEGER NOT NULL,  `fecha` datetime NOT NULL,  `largo` INTEGER NOT NULL,  `operador` INTEGER NOT NULL,  `voa_version` SMALLINT NOT NULL,  CONSTRAINT `pk_tronco` PRIMARY KEY (`tronco_id`) ) TYPE = InnoDB' : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE = InnoDB' at line 1 BusinessClasses 

    I have done some research, and I found somewhere in the web that the solution is to replace 'TYPE = InnoDB' with 'Engine = InnoDB' if the MySQL server version is 5.5 which is my case. I checked that, and the proposed solution worked fine. The problem is that I can get my application to compile.

    Any possible workaround?

    Best regards,

  4. Ady
    Ady avatar
    589 posts

    Posted 21 Jan 2011 Link to this post

    Hi Dmitry Semenov,

     Thank you for pointing this out. We have fixed this problem and the fix will be available in the next build we release. As a workaround you could use the Schema handling API to obtain the required SQL, update the 'TYPE=InnoDB', to 'ENGINE=InnoDB' for each 'create table' statement and then execute it.

    the Telerik team
    Accelerate your learning with industry's first Telerik OpenAccess ORM SDK. Download today.
  5. gmendez
    gmendez avatar
    82 posts
    Member since:
    Jun 2012

    Posted 25 Jan 2011 Link to this post

    I am  not Dmitry Semenov :) ,and thanks for the workaround.

Back to Top