Thanks, I did have a look at it and it seems that I could use embedded mysql with no conffiles at all. :-) I like it becouse I would prefer application configuring mysql based on its own config or status and not having spread conffiles for each used library. Besides, various applications using this library and editing some mysql conffile at user home (/home/user/.my.cnf) could finish in a mess.
El jue, 04-11-2004 a las 17:51 +0200, Gleb Paharenko escribió: > Hi. > > > > You may tell MySQL where the data files are stored in the argc, > > when you are calling mysql_server_init. Also you may put other > > server variables into this array. > > > > I think, MySQL can do most tasks, which you are looking for. > > > > See: > > http://dev.mysql.com/doc/mysql/en/Server_system_variables.html > > > > > > > > txemi <[EMAIL PROTECTED]> wrote: > > > I cannot see in mysql online manual Embedded example > > > (http://dev.mysql.com/doc/mysql/en/libmysqld_example.html) any pathname > > > telling where de database will be saved in disk. So I suppose it must be > > > some existing database especified on some configuration file. > > > > > > Could be embebbed mysql be a replacement to sqlite for programs that > > > just want to create some database in some specified file with no > > > configuration if possible? > > > > > > I was thinking of embebbed mysql as a way for user unprivileged desktop > > > programs creating databases at user's home. The apps I was thinking of > > > were personal databases, addressbooks and so. For being embebbed and > > > created on a personal file or dir they would be easy to create, update > > > and remove. Besides, for using mysql backend it would be powerful (lot > > > of features as foreing indexes and constraints and complex sql commands) > > > and I suppose easy to export data for latter use in other mysql > > > databases and so if neccesary. > > > > > > So I could thank any opinion on this to help me know if embedded mysql > > > could fit my needs or I would better use a simpler solution as sqlite. > > > > > > The things I would try to avoid: > > > - An unprivileged desktop user needing to edit system config. > > > - Needing to edit config files. Better to set up everything inside the > > > application. > > > - Being able to create, edit and remove database from application. No > > > need for extra config. > > > > > > thanks, > > > txemi. > > > > > > > -- > For technical support contracts, goto https://order.mysql.com/?ref=ensita > This email is sponsored by Ensita.NET http://www.ensita.net/ > __ ___ ___ ____ __ > / |/ /_ __/ __/ __ \/ / Gleb Paharenko > / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] > /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET > <___/ www.mysql.com > > > > -- ______________________________ < hola, soy una firma horrible > ------------------------------ \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || email: [EMAIL PROTECTED] web: http://txemi.webhop.org web2: http://txemi2.webhop.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
