[geeklog-devel] Geeklog and MySQL 3.22

[Tony Bibbs]

Changing to date_sub probably won't hurt performance and teh benefit of 
having GL workign on 3.22.x good enough to warrant (though I'm still 
laughing my ass off that any reputable ISP would still be using that 
version)

As for indexes, I think the easy thing is to add a new array $_INDEXES in 
teh mysqltableanddata.php which are a series of alter table commands to 
add indexes.  Then teh installer would need to 1) connect and create DB 
structures 2) get the mysql version 3) if version > 3.22 then execute 
everything in $_INDEXES.

That way you have something that I think is easier to maintain with 
subsequent versions, no?

--Tony

 On Wed, 12 Feb 2003, Dirk Haun wrote:

> Apparantly, many hosting services are still running MySQL 3.22.something
> :-/ Among them is, for example, Germany's second biggest hoster (1.5
> million .de domains).
> 
> So it may be worthwhile to investigate what's keeping Geeklog from
> working on MySQL 3.22. One of the users of geeklog.info already spent
> some time with this and found a simple solution for the problem with the
> What's New block.
> 
> All you need to do is change the syntax for subtraction of times from '-'
> to 'date_sub', e.g.
> 
> $sql = "SELECT count(*) AS count FROM {$_TABLES['stories']} WHERE (date
> >= (NOW() - INTERVAL {$_CONF['newstoriesinterval']} SECOND)) AND (date <=
> NOW()) AND (draft_flag = 0) AND (" . $nesql . ")"; 
> 
> to 
> 
> $sql = "SELECT count(*) AS count FROM {$_TABLES['stories']} WHERE (date
> >= (date_sub(NOW(), INTERVAL {$_CONF['newstoriesinterval']} SECOND))) AND
> (date <= NOW()) AND (draft_flag = 0) AND (" . $nesql . ")"; 
> 
> (and a similar change in another place).
> 
> Question for the (My)SQL gurus: Do you see any problems with this.
> Performance-wise, compatibility, etc?
> 
> 
> The other issue people will run into is actually at install time when
> they get errors like "1121: Column 'date' is used with UNIQUE or INDEX
> but is not defined as NOT NULL". The install docs mention this problem,
> but the solution there (removing two line from mysql_tableanddata.php) is
> out of date since we introduced additional index fields in 1.3.7.
> 
> Not sure what we could do there other than providing a second version of
> mysql_tableanddata.php without the additional index fields ...
> 
> bye, Dirk
> 
> 
> 

-- 
Tony Bibbs          "I guess you have to remember that those who don't
tony at tonybibbs.com  hunt or fish often see those of us who do as      
                    harmlessly strange and sort of amusing. When you  
                    think about it, that might be a fair assessment." 
                    --Unknown