For a new project which has to target Linux and Windows, I am searching for a solution to support MySQL (or MariaDB).
Because we have to support those different platforms I wish to work on DNX Core5.0. However I can't find any nuget packages / connectors which I can use to connect to the database. the one that i find are not supported by DNX core 5.0.
Is there a way to connect to mysql in DNX core 5.0 ? Or do you have to fall back on ODBC connections, i don't know if this would work...
Further i was searching for an ORM to support this, my research till now found out that
Entity Framework 7 is not supporting MySQL at this moment. (and EF is not my favorite ORM at this moment)
NHibernate: Currently nobody is working on it and it will be difficult (breaking changes) to port it to DNX Core
Dapper: (MicroORM I know ...): This is supporting DNXCore but i need a vallid IConnection which I can't create.
Thanks for your feedback!
Rob
I asked a similar question a couple of weeks ago. There is no MySql connector for DNX Core. I had to fall back to DNX 4.5.1 and was able to use MySql with Entity Framework in a project that's running inside a Docker container. Also see the response to my question.
Related
Symfony 2.8 requires PHP version to be at least 5.3.9, however nothing is mentioned regarding Apache and MySQL versions in the documentation. What are the minimal requirements for them?
Apache and MySQL version are not exactly relevant there: Apache acts merely as a caller to PHP (in the most common mod_php stack), so it does not interact directly with Symfony. Plus Apache release cycles tend to be longer (2.2 from 2005 is still around).
Regarding MySQL, it concerns Doctrine exactly, especially the DBAL - Database Abstraction Layer. Doctrine platforms documentation does not state much about it, we can infer it supports MySQL 5.0+.
Of course, the higher you can go is the better. PHP 5.3 is not supported anymore, nor PHP 5.4 or PHP 5.5 (security bugs supports stopped last week). Apache 2.2 you need the very last "patch" version. MySQL dramatically improved in 5.5+.
If nothing is mentionned in the documentation,then it means any version can be used most of the time.
I think you should simple use the latest version available in your distributions's repository.
I just registered a hosting service from www.amhosting.com and they said that the Server support MySQL and .Net 3.0 only while the site I am installing is DNN 7 which is running with MSSQL and .Net 4.0.
So what is the solution for this case?
Could I run DNN 7 in .net 3.0 environment?
or should I downgrade the DNN to lower version that is able to run in .net 3.0?
How to configure the DNN site to run with MySQL?
Thanks a lot.
Cheers,
Timmy
I think you should change your hosting solution.
From what I know DNN7 only works with .NET 4.0 / 4.5
MySql - god forbid, you're in a world of pain. I have heard about attempts to make the DNN Core compatible with MySql... but it's only the Core, and any such projects would be outdated in a matter of months, as DNN does release quite often.
Talking about third party modules, which sooner or later you'll be bound to download from codeplex or buy from Dnn store - forget about. no dnn developer out there provides scripts for mysql.
Good luck!
As Greg states, you won't have an easy time getting DNN working in 2.0 (there was no 3.0, but 3.5 exists) with MYSQL, and you will be limited based on the "provider" for MYSQL.
Go with another hosting company that does Windows Hosting with MSSQL options, there are plenty of them out there for low cost, you'll save a lot more money changing hosting, than you will trying to get mysql working with DNN, and you won't have any upgrade options available to you.
We are currently running Liferay 6.0.6 connected to Oracle 11.2.0.2.0. Due to business requirements around licensing of Oracle I need to investigate moving this over to MySQL 5.5 with InnoDB. Downtime will be acceptable for this migration.
Can I just copy code and data structure over?
Would a new installation with MySQL be best, and then copy data over from the Oracle installation?
Has anyone here done this before?
On the side of migrating the database, the easiest way to do this is to go to the ControlPanel, under Server Administration you'll find a page with a Database migration UI. This will read from your current database (e.g. oracle) and write to a database that you configure on that UI. Make sure that nobody is accessing the portal during that time - this feature has been created specifically for migrating databases: There might be some differences between the databases, that will automatically be "translated" in this progress.
On a somewhat related side note: If you want to get updates and fixes (including security), you should consider to upgrade to a maintained version, CE or EE. 6.0 CE (which is what 6.0.6 is) has end-of-lifed a while ago. 6.0 EE is still available, as well as 6.1 CE and EE.
Edit in 2017: Note that this feature is no longer supported in Liferay 7 and DXP: The database migration tool doesn't cover (all of) the module's tables.
I've read through a number of pages detailing the version differences between the different MySQL versions, but none of them have given me a real clear picture as to what is best for the application I am making. I'm in the process of building a CRM which will handle 20,000 customers at launch and built on a LAMP stack. The OS will either be CentOS or FreeBSD.
Right now for test purposes we've been using a MySQL 5.0 server for the database, but we are wondering which version we should use for production. If anyone could give some thoughts as to the pros and cons of using 5.0 vs 5.1 vs 5.5 vs 5.6 in the context of a CRM application, it would be most appreciated.
TL;DR 5.5
For a new software rollout, it makes sense to integrate and do final testing with the latest generally available (GA) release of your infrastructure components.
Right now that's 5.5.20 of the MySQL community server. 5.6.x is considered a development release. It probably doesn't make sense for you to try to do integration and final testing with such a release, unless it offers a new feature that's a critical success factor for your new software. (But then you should ask yourself whether it makes sense to make your product dependent on exotic new features in unfinished dbms releases.)
EDIT... #rkosegi has a good point. If you're going to deploy on an enterprise grade linux server distro like Red Hat Enterprise Linux (rhel) use the version it supports. 5.1 works fine.
I think better you should use v5.1.XX because it's in active development state and stable too.
MySQL has stopped working on v5.0 i guess extend support also will expire soon.
http://dev.mysql.com/doc/refman/5.0/en/
I am creating application for MAC using cocoa framework, I would like to know how and what are the ways i can connect to MySql database using cocoa framework.
You might want to look into http://www.sequelpro.com/docs/Source_Code. They seem to have resurrected the original MySQL-Cocoa code and it seems to be under active development. The other option is the commercial MacSQL Framework.
Edit: You might also want to look at the following tutorial. It is a great introduction in using the libmysqlclient and even provides a sample Xcode project.
Short answer: You can't, at least not directly.
The Cocoa Framework doesn't have a database driver, generic or otherwise (CoreData notwithstanding). In order to connect to a mysql database you need to use the aptly named libmysqlclient. This library is not included with Xcode, and as such will have to be downloaded (and probably built) separately: You can get it from here.
You'll probably have to distribute the library with your application, license issues might result.
Edit: It seems as if a library for connecting to the mysql database should be installed together with a MySQL server install. If the application will only need to run on machines where MySQL is installed, you might get away with linking to this.