difference between UniDAC and MyDAC for mySQL?

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
docH
Posts: 59
Joined: Sun 22 Dec 2013 15:18

difference between UniDAC and MyDAC for mySQL?

Post by docH » Fri 27 Dec 2013 17:59

I have downloaded trial versions of both UniDAC and myDAC to connect Delphi to a remote mySQL database, run some sql, return the results and display them on a form.

Both connection components seem to work using either table or query components conected to a dbgrid.

I note that UniDAC also seems to be able to connect to many other databases as well (I also use SQLlite3) but is half the price of MyDAC.

Am I missing something here, why would I want myDAC if UniDAC is better and cheaper?

docH
Posts: 59
Joined: Sun 22 Dec 2013 15:18

Re: difference between UniDAC and MyDAC for mySQL?

Post by docH » Fri 27 Dec 2013 18:39

Replying to myself but am still confused so if anyone has any clear information I'd be grateful.
It appears that UniDAC is OK if you don't want special server specific features, otherwise you need myDAC. That's good, so far it looks like UniDAC will do.
BUT it also appears that the 'standard' edition of UniDAC is useless as it does not come with any providers - and there is no info that I can find on this site that tells you were to get them and how much they cost. It seems you have to get the 'professional' edition (which costs more than myDAC) before you can do anything. So why sell the standard edition of UniDAC if you can't do anything with it?

Adding to the confusion is that this site does not say which editions get downloaded for the 60 day trial, so you can't tell which version you need to buy as you don't know if you are using features that won't be there in the paid for version. I'm guessing the trials are the pro version so I can't really see whether the standard versions of myDACX or UniDAC will work for me.

Anyone able to enlighten me further?

AndreyZ

Re: difference between UniDAC and MyDAC for mySQL?

Post by AndreyZ » Mon 30 Dec 2013 07:06

UniDAC Standard Edition includes only basic components and does not include any database server providers. UniDAC Standard Edition is intended to be used by developers that already use other DAC products (SDAC, ODAC, MyDAC, etc.). In this case, providers for UniDAC are supplied with these DAC products. You can find information about UniDAC editions at http://www.devart.com/unidac/editions.html . The first paragraph explains the purpose of the UniDAC Standard edition. Also, this page shows the difference between UniDAC editions and explains the set of components and features that are present or not in each particular edition.

UniDAC provides a transparent server-independent interface for working with different databases, such as MySQL, SQL Server, Oracle, InterBase, and others. However, MyDAC has access to more server-specific features of MySQL Server, like MyBackup, MyServerControl, and MyEmbConnection. You can learn more about MyDAC features here: http://devart.com/mydac/features.html , and about UniDAC features here: http://devart.com/unidac/features.html .
If you want to use server-specific functionality of each database server, it's better to use specific DAC components. If you are not interested in using server-specific features, you can use UniDAC.

You can find all information about UniDAC Trial version at http://www.devart.com/unidac/download.html . The first paragraph says:
UniDAC Trial Edition is a fully functional Professional Edition

docH
Posts: 59
Joined: Sun 22 Dec 2013 15:18

Re: difference between UniDAC and MyDAC for mySQL?

Post by docH » Mon 30 Dec 2013 12:06

Thank you, I did read all that which is partly why I posted my question. If a developer already has a few separate components like myDAC etc. which offer more facilities but for specific databases then I can't see the reason for Unidac standard if I still need to get the database specific provider. eg If I already have separate components for say MySQL, SQLite and Access and I want to get one for say PostgreSQL then Unidac standard won't help unless I also buy PgDAC to get the provider - in which case I don't need UniDAC as PgDAC offers more facilities anyway.

And why can't companies offer trials of the editions they sell? It's not much good selling a standard version, which might do what I want, if the only one I can trial is the all singing and dancing one that gives a false impression of what I will get when I buy the standard edition.

I would prefer to trial the standard, find it won't quite do what I want and so buy the pro edition, instead of trialing the pro edition (withought realising it), buy the standard and find I've wasted my money and time as it won't do what I thought it would.
Better still, offer a trial of every edition sold and let the customer decide.

AndreyZ

Re: difference between UniDAC and MyDAC for mySQL?

Post by AndreyZ » Mon 30 Dec 2013 12:44

UniDAC Standard Edition is a cost-effective solution when you already have several DAC products and want to work with different database servers in a unified way in one application. For example, you have MyDAC and SDAC and you want to work with MySQL and SQL Server using the same components. This can be achieved by using UniDAC Standard Edition. Of course, the same can be achieved using UniDAC Professional Edition, but it costs more than twice as high. It is up for you to decide what UniDAC edition is more appropriate for you.

Trial edition of any product is usually the most functional edition from all others.

Post Reply