You need to download the MySQL-4.0 source and compile for
embedded-server. This is a library that you link your programs to.
It is used for small devices, like what we are doing here.
I haven't found any docs on it yet, but the header files give plenty or
explaination.
Hope that helped
Brian Austin
On Thu, 9 Aug 2001, Alex Page wrote:
> From: "Shawn P. Garbett" <[EMAIL PROTECTED]>
> Sent: Thursday, August 09, 2001 3:07 PM
> Subject: Fwd: Re: Embedding MySQL in an application
>
>
> > The real point is, that a user can take the product out of shrink rap,
> > install it, run the program and never fiddle one iota with installation of
> > MySQL or even know that MySQL is running on the system.
>
> So what you're essentially talking about is embedding the MySQL *binary* in
> an
> application? There are a lot of reasons why this is a bad idea - it'll
> replicate unnecessarily if more than one application does this, you won't be
> able to upgrade MySQL (to, say, fix security holes) without upgrading the
> application...
>
> ...but I suppose that massively monolithic, repetitive code is the way of
> the Windows world...
>
> > MySQL is entirely
> > embedded within the application. Sure I could write drivers in the
> database
> > module that did all this with flat-files, but ugh what a horrible thought.
>
> In perl:
>
> use DBI;
> if ( -x /usr/local/mysql/bin/mysql ) {
> require DBD::mysql;
> } else {
> require DBD::CSV;
> }
>
> But hey, perl's good like that.
>
> > The plan is in the future as the product line grows is to eventually tie
> > several products together through a seperate database engine, or have then
> as
> > stand-alone packages.
>
> This depends on your target platform. With your talk of Microsoft, I presume
> that
> you're developing for a Windows platform. The best way to do this, IMHO,
> would be
> to have the installation program for *your* application check to see if
> MySQL is
> installed (by poking in the registry?), and download and install it (perhaps
> invisibly) if it isn't (or you could include MySQL with the CD of your
> application, licensing issues permitting).
>
> If you then want to port to (say) Linux, you could have the program package
> have a dependency on MySQL (this seems to work very well in Debian, not sure
> about RPM-based distribution) which would do exactly the same - check for
> MySQL on install, and install it invisibly if it's not there.
>
> Hope this is of some use,
>
> Alex
> --
> Alex Page, IT Department, Solid State Logic
> E-Mail: [EMAIL PROTECTED]
> Phone: +44 (0) 1865 842 300
> Web: http://www.solid-state-logic.com
>
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
