Thanks for the input, I have posted also on the database-discuss list. Are there defaults for where to put application configuration files?
And also for MySQL there might be a default for where to put database logfiles and datafiles. Since datafiles for a database could be rather big, a default location might be a bad idea. And for packaging, should it be available as one package, or is it standard to offer different packages for client, server, docs, source, etc? Jan S David.Comay at Sun.COM wrote: >> First we want to use studio12 as compiler, as that gives quite much >> higher performance gain (using new compiler flags in studio12). >> We would like databases to work as good as possible on Solaris, and >> especially we would like to have performance numbers favorable over >> Linux :) >> I see that the compiler for webstack is studio11, is it possible to >> upgrade to studio12? Or can we use studio12 for MySQL? > > All OpenSolaris components are built with the standard Common Build > Environment or CBE. At the moment, the C compilers used for this are > Studio 11 (plus patches) and the bundled gcc 3.4.3. I'm not aware at > the moment of a precise date for upgrading to Studio 12 although work > is underway on evaluating it from regression and performance > perspectives. > > The official Studio part of the CBE can be found internally via the > following automount point > > /ws/onnv-tools/SUNWspro/SS11 > > or externally via > > > http://opensolaris.org/os/community/tools/sun_studio_tools/sun_studio_11_tools/ > > > >> Second, which MySQL components should be included? They have three >> client components that all seems quite useful to include. This is >> Connector/J for JDBC, Connector/ODBC for ODBC and a PHP client library. >> Should also any GUI tools be included? > > I would recommend also asking the database-discuss at opensolaris.org > community for their input too. > > dsc >
