Hi,

I'm a database guy but have barely used mySQL. What I intend to do is
this:
export an Access database with 10 to 15 tables (not much seed data
though) to mySQL on Mac.
Here, I have a bunch of questions.

a) Migration options and constraints (I'm on Windows OS)
option 1
download and install mySQL myself
export the db: Access db -> ODBC driver -> mySQL (for Windows)
generate ddl db script and export data dump script(s)

having someone with Mac to download & install mySQL for Mac
run the db scripts that I generated and create this database with
data on the mySQL for Mac server
(not sure how easy or difficult this process would be for a non-
techie Mac user...)

b) With regard to mySQL for Mac
1. Would Mac OS X ver. 10.6 (x86, 32-bit) work under Mac OS X 64 bit
as well?

2. Of DMG Archive and Compressed TAR, which one is easier for
installation?

c) Could mySQL for Mac installation be automated with an installation
script something?
Because this db is a component of a software package.

And let me know if you know another simpler or easier option.

Thank you very much.

justaguy wrote:
May be easier to export as CSV and import using LOAD command

All mac users are non techie.

On Nov 25, 6:29*am, The Natural Philosopher <t... (AT) invalid (DOT) invalid>
wrote:
"May be easier to export as CSV and import using LOAD command "
Sorry, this won't do it. The database would be used for data storage.

Thanks for the note tho.

On 2011-11-25 00:57, justaguy wrote:
[...]
If you have not done so already I advise you to study the mysql license
before bundling it with your application. I have never bundled anything
with mysql myself, so I not sure what it says exactly, but there have
been numerous discussions on this subject in the past. The license might
not be a problem for you, but better safe than sorry.


/Lennart

justaguy wrote:
I assumed that once the data transfer had been done Access would be
ditched..Do I understand you want to keep Access as a front end?

In which case the term is not 'export' in my book: Export is a once and
or all transfer of data into a different format.

which is easiest to load into a MySQL database using the LOAD command.

On Nov 25, 1:00*pm, Lennart Jonsson <erik.lennart.jons... (AT) gmail (DOT) com>
wrote:
"The license might not be a problem for you, but better safe than
sorry. "
Good thought. In the meantime, mySQL has always been open source...
I know Oracle bought it some time ago... but since it does not come
with any tools to perform database management tasks, it would be real
hard sell to market it as a commercial DBMS... wouldn't you agree?
Besides, even for Oracle itself, it is said 90% of its profit comes
from consulting fees.

justaguy:

You appear to believe that an open source product can be integrated
into any software package without restrictions or costs.
Please reconsider, and refer to
http://mysql.com/about/legal/licensing/index.html as a starting point.
Chances are, that you need either pay for the product, or offer your
own package as open source software under GPL, too.

--
Erick

On Nov 25, 3:33*pm, "Erick T. Barkhuis" <erick.use-... (AT) ardane (DOT) c.o.m>
wrote:
Thanks for the mySQL license info. It's absurd for such a non ANSI
'92 standard bare-bone database engine, with a big120+ MB file size,
Oracle is charging money for its use... probably I've wasted 4-5
hours.

On Thu, 24 Nov 2011 15:57:42 -0800 (PST), justaguy
<lichunshen84 (AT) gmail (DOT) com> wrote:

http://www.sqlite.org/

Best regards,
--
( Kees Nuyt
)
c[_]

On Nov 25, 5:45*pm, Kees Nuyt <k.n... (AT) nospam (DOT) demon.nl> wrote:
Yeah, I've taken at a good look at this guy as well. I can read C
code but compilation etc. is going to be a mess (believe me...). Just
curious, why don't they create some plain executable for Windows or
Mac or Linux (basic stuff) and make it configurable... sort of as
they did for command line utility...

Thanks tho.