Yes I basically agree with you, that's why I wasn't so fond
of making it an
option but a default select. However, I think james
suggestion is a good
one. I also still think it doesn't plain work with InnoDB as
Default on
server as it is now. But I will check in on that one.
I will post adodb upgrade patch in separate post as I think
it's good to
keep the issues separated. I feel rather eager to have adodb
updated though
asap.
y
> -----Original Message-----
> From: bitweaver-core-bounces lists.sourceforge.net
[mailto:bitweaver-
> core-bounceslists.sourceforge.net] On Behalf Of
Christian Fowler
> Sent: 27 November 2007 18:31
> To: bitweaver-corelists.sourceforge.net
> Subject: Re: [bitweaver-core] R2 and MySql
>
>
> At this point, I think we should do as little as
possible. If you want
> InnoDB as your table types, the user should configure
that as the
> default
> type for his particular DB. If they don't have that
ability, they will
> need to get a new host, or new database. i.e. the needs
of the user are
> directly proportional to the skill and control they can
exerpt. Even if
> InnoDb may be technically superior, it is not
necessarily the "better"
> solution for those that don't understand it.
>
> My advice is to setup InnoDB as the default for your
system. Let's fix
> the
> install failures with that. For the installer, we can
recomend the
> changes
> for those that have InnoDB capable db's, but not
defaulted.
>
> This is how we handle the GD graphics engine, which is
more common but
> infrerior. We offer instructions on how to get
MagickWand going.
>
> This get's rid of lots of problems and code. It's not
bitweaver's job
> to
> make sure people are running the optimal configuration.
The best we can
> do
> is educate, and let the administrator make their own
decisions.
>
> - spider
>
>
>
> On Tue, 27 Nov 2007, James H Thompson wrote:
>
> > Another consideration, innodb and myisam are not
the only two choices
> for
> > table types.
> > Falcon is coming, and there are some other 3rd
party choices
> available now.
> > So it would be good to make it easy to change the
selected storage
> engine
> > when installing.
> >
> >
> > ----- Original Message -----
> > From: "Yettyn" <yettynastrocalc.com>
> > To: <bitweaver-corelists.sourceforge.net>
> > Sent: Tuesday, November 27, 2007 5:13 AM
> > Subject: Re: [bitweaver-core] R2 and MySql
> >
> >
> >>>
> >>> For that reason, I am opposed to exclusive
InnoDB support, however,
> I
> >>> think it is a great idea to offer an
option during install. This
> thread
> >>> talks about how to detect available
engines:
> >>> http://phplens.com/lens/lensforum/msgs.php?id=17009&a
mp;x=1
> >>> Which is a good option, and defaulting to
INNODB for systems that
> >>> support
> >>> it.
> >>>
> >> So, I now have a routine that check for
support of InnoDB, then if
> we are
> >> offering the option to choose either of MyIsam
and InnoDB then this
> need
> >> to
> >> be stored somehow, in db or config_inc.php? I
think db is the better
> >> alternative as when config_inc.php is created
we have no connection
> to db
> >> (I
> >> think) and hence cannot make a decision in
this matter.
> >>
> >> There is another little dilemma here as well.
If not 'mysqli'
> extension is
> >> selected, but InnoDb then we need to use
'mysqlt' instead of 'mysql'
> and
> >> this value is stored in config_inc.php so
somehow it then makes
> sense to
> >> store the InnoDB flag as well in
config_inc.php - I assume this file
> can
> >> be
> >> updated at a later stage during installation
as well?
> >>
> >> I am not sure though if it's worth the trouble
or even make sense to
> make
> >> this an option. Our code makes heavy use of
transactions, and if
> InnoDB is
> >> available it's just plain stupid not to use
it. So I am in favour of
> >> simply
> >> check for and use InnoDB if available,
otherwise fall back to
> MyIsam, and
> >> if
> >> InnoDB is used use 'mysqlt' unless 'mysqli'
extension is selected.
> >>
> >> y
> >>
> >>
> >>
------------------------------------------------------------
--------
> -----
> >> This SF.net email is sponsored by: Microsoft
> >> Defy all challenges. Microsoft(R) Visual
Studio 2005.
> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>
_______________________________________________
> >> bitweaver-core mailing list
> >> bitweaver-corelists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/bitweave
r-core
> >
> >
> >
------------------------------------------------------------
---------
> ----
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio
2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > bitweaver-core mailing list
> > bitweaver-corelists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitweave
r-core
> >
>
> [ / Christian Fowler | spider AT
viovio.com
> [ >X< http://www.viovio.com/sp
ider | http://www.bitweaver.
org/spider
> [ / ~~~ always plan in the millions ~~~
>
>
------------------------------------------------------------
-----------
> --
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> bitweaver-core mailing list
> bitweaver-corelists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitweave
r-core
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
bitweaver-core mailing list
bitweaver-corelists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitweave
r-core
|
