[geeklog-devtalk] geeklog-devel digest, Vol 1 #275 - 7 msgs

[geeklog-devel-request at lists.geeklog.net]

Send geeklog-devel mailing list submissions to
	geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
	geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

   1. Re: The first 1.3.9rc1 bugs are in ... (Dirk Haun)
   2. Re: The first 1.3.9rc1 bugs are in ... (Dirk Haun)
   3. MySQL issue / table lockups (Dirk Haun)
   4. Re: MySQL issue / table lockups (Tony Bibbs)
   5. Re: The first 1.3.9rc1 bugs are in ... (Blaine Lang)
   6. Re: The first 1.3.9rc1 bugs are in ... (Tony Bibbs)
   7. Re: The first 1.3.9rc1 bugs are in ... (Tony Bibbs)

--__--__--

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...
Date: Wed, 18 Feb 2004 19:37:26 +0100
Organization: Terra Software Systems
Reply-To: geeklog-devel at lists.geeklog.net

Vinny,


>Found a slightly deeper problem that is all tied up in this.  With the 

>below change the reply-to-link is now broken (it responds to the 

>comment/story an extra level up).


Yep, noticed this as well.



>If you give me some guidance on how you want to handle this I can code 

>up the changes.


I would have preferred a solution that didn't require theme changes, but
if that's not possible, I leave it up to you to decide.



>Write cvs access would be convenient at this point. ;)


Agreed. Tony?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.tinyweb.de/


--__--__--

Message: 2
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...
Date: Wed, 18 Feb 2004 19:43:16 +0100
Organization: Terra Software Systems
Reply-To: geeklog-devel at lists.geeklog.net

I'm a bit short on time this week, so I try to delegate as much as
possible ;-)

Next person on my list: Blaine.

I've received a report from someone who has a lot of blocks on his site.
Apparantly, since the new block list code will number them in steps of
10, it will eventually come up with block order numbers in the 300s. But
Geeklog only allows order numbers up to 255.

I'd prefer a solution that doesn't require theme and database changes,
but if that's not possible or would require too much work, then so be it ...

bye, Dirk


-- 
http://www.haun-online.de/
http://mypod.de/


--__--__--

Message: 3
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Date: Wed, 18 Feb 2004 20:29:54 +0100
Organization: Terra Software Systems
Subject: [geeklog-devel] MySQL issue / table lockups
Reply-To: geeklog-devel at lists.geeklog.net

Here's some other issue altogether, slighlty edited from IRC:

<mvonahn> I have noticed that the hit couter can lock the whole stories table
<mvonahn> when viewing the story
<mvonahn> what happens when you have large number of stories and someone
performs a search
<mvonahn> is that update gets locked
<mvonahn> then everything behind the update gets locked
<mvonahn> so, basically a long search on an active site can lock the
whole site
<mvonahn> it can be solved in 2 ways
<mvonahn> changing the stories table type to innodb
<mvonahn> or, what I have been doing, splitting the table
<mvonahn> a stories and a stories_stat
<mvonahn> the stories table is myisam so I an use fulltext indexing and
the stat table is innodb to prevent locks
<dhaun>   I see - innodb is supported in MySQL since when?
<mvonahn> late 3
<mvonahn> I ubderstand the problem of supporting install on ISP's with
old setups
<dhaun>   mysql.com isn't very clear on the version number for innodb
support. it mentions 3.23.34a but the wording indicates it may not have
been availabe in default installs right away ...
<dhaun>   we have user with versions down to 3.22.something :-/
<mvonahn> that may be, I seem to remember having to dl the max install to
get it originally
<mvonahn> or something like that
<mvonahn> yeah, that is unfortunate
<mvonahn> maybe an install option for those that know they have innodb
installed
<mvonahn> to set table types on appropriate tables
<dhaun>   but maybe putting all the stats into a separate table would be
a way around it - those that run into the problem could then change the
type of the table
<mvonahn> exactly
<mvonahn> shouldn't affect anything
<mvonahn> coul dbe posted as a note for performance on large systems
<dhaun>   k, stuff to think about for 1.3.10 :P
<mvonahn> so far that is the only scalability issue I have come across

Comments?

bye, Dirk


-- 
http://www.haun-online.de/
http://geeklog.info/


--__--__--

Message: 4
Date: Wed, 18 Feb 2004 15:36:27 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] MySQL issue / table lockups
Reply-To: geeklog-devel at lists.geeklog.net

Any reason why we don't ship new GL installs with option of Innodb or 
MyISAM with a default of Innodb?  Or to be even slicker, once we know 
what version of MySQL supported Innodb we can query it before creating 
any new tables and figure it out on the fly.

--Tony

Dirk Haun wrote:

> Here's some other issue altogether, slighlty edited from IRC:

> 

> <mvonahn> I have noticed that the hit couter can lock the whole stories table

> <mvonahn> when viewing the story

> <mvonahn> what happens when you have large number of stories and someone

> performs a search

> <mvonahn> is that update gets locked

> <mvonahn> then everything behind the update gets locked

> <mvonahn> so, basically a long search on an active site can lock the

> whole site

> <mvonahn> it can be solved in 2 ways

> <mvonahn> changing the stories table type to innodb

> <mvonahn> or, what I have been doing, splitting the table

> <mvonahn> a stories and a stories_stat

> <mvonahn> the stories table is myisam so I an use fulltext indexing and

> the stat table is innodb to prevent locks

> <dhaun>   I see - innodb is supported in MySQL since when?

> <mvonahn> late 3

> <mvonahn> I ubderstand the problem of supporting install on ISP's with

> old setups

> <dhaun>   mysql.com isn't very clear on the version number for innodb

> support. it mentions 3.23.34a but the wording indicates it may not have

> been availabe in default installs right away ...

> <dhaun>   we have user with versions down to 3.22.something :-/

> <mvonahn> that may be, I seem to remember having to dl the max install to

> get it originally

> <mvonahn> or something like that

> <mvonahn> yeah, that is unfortunate

> <mvonahn> maybe an install option for those that know they have innodb

> installed

> <mvonahn> to set table types on appropriate tables

> <dhaun>   but maybe putting all the stats into a separate table would be

> a way around it - those that run into the problem could then change the

> type of the table

> <mvonahn> exactly

> <mvonahn> shouldn't affect anything

> <mvonahn> coul dbe posted as a note for performance on large systems

> <dhaun>   k, stuff to think about for 1.3.10 :P

> <mvonahn> so far that is the only scalability issue I have come across

> 

> Comments?

> 

> bye, Dirk

> 

> 


--__--__--

Message: 5
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...
Date: Wed, 18 Feb 2004 20:06:18 -0500
Reply-To: geeklog-devel at lists.geeklog.net

Well we could change the interval but I like 10 :)
Only 2 options - change the interval or change the field type that I see.

It could be changed to use 2 as the interval and that still allows someone
to manually enter a number to fit between 2 blocks.

Blaine
----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Wednesday, February 18, 2004 1:43 PM
Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...



> I'm a bit short on time this week, so I try to delegate as much as

> possible ;-)

>

> Next person on my list: Blaine.

>

> I've received a report from someone who has a lot of blocks on his site.

> Apparantly, since the new block list code will number them in steps of

> 10, it will eventually come up with block order numbers in the 300s. But

> Geeklog only allows order numbers up to 255.

>

> I'd prefer a solution that doesn't require theme and database changes,

> but if that's not possible or would require too much work, then so be it

...

>

> bye, Dirk

>

>

> -- 

> http://www.haun-online.de/

> http://mypod.de/

>

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devel



--__--__--

Message: 6
Date: Thu, 19 Feb 2004 06:56:01 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...
Reply-To: geeklog-devel at lists.geeklog.net

Vinny, you have an email with your CVS account info.

--Tony

Dirk Haun wrote:

> Vinny,

> 

> 

>>Found a slightly deeper problem that is all tied up in this.  With the 

>>below change the reply-to-link is now broken (it responds to the 

>>comment/story an extra level up).

> 

> 

> Yep, noticed this as well.

> 

> 

> 

>>If you give me some guidance on how you want to handle this I can code 

>>up the changes.

> 

> 

> I would have preferred a solution that didn't require theme changes, but

> if that's not possible, I leave it up to you to decide.

> 

> 

> 

>>Write cvs access would be convenient at this point. ;)

> 

> 

> Agreed. Tony?

> 

> bye, Dirk

> 

> 


--__--__--

Message: 7
Date: Thu, 19 Feb 2004 06:58:08 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...
Reply-To: geeklog-devel at lists.geeklog.net

I tend to order my blocks in increments of ten as well.  Just a 
preference so I'd vote for the db change since that seem like the 
'right' way though I do appreciate the hassle that creates.

Blaine Lang wrote:

> Well we could change the interval but I like 10 :)

> Only 2 options - change the interval or change the field type that I see.

> 

> It could be changed to use 2 as the interval and that still allows someone

> to manually enter a number to fit between 2 blocks.

> 

> Blaine

> ----- Original Message ----- 

> From: "Dirk Haun" <dirk at haun-online.de>

> To: <geeklog-devel at lists.geeklog.net>

> Sent: Wednesday, February 18, 2004 1:43 PM

> Subject: Re: [geeklog-devel] The first 1.3.9rc1 bugs are in ...

> 

> 

> 

>>I'm a bit short on time this week, so I try to delegate as much as

>>possible ;-)

>>

>>Next person on my list: Blaine.

>>

>>I've received a report from someone who has a lot of blocks on his site.

>>Apparantly, since the new block list code will number them in steps of

>>10, it will eventually come up with block order numbers in the 300s. But

>>Geeklog only allows order numbers up to 255.

>>

>>I'd prefer a solution that doesn't require theme and database changes,

>>but if that's not possible or would require too much work, then so be it

> 

> ...

> 

>>bye, Dirk

>>

>>

>>-- 

>>http://www.haun-online.de/

>>http://mypod.de/

>>

>>_______________________________________________

>>geeklog-devel mailing list

>>geeklog-devel at lists.geeklog.net

>>http://lists.geeklog.net/listinfo/geeklog-devel

> 

> 

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devel



--__--__--

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel


End of geeklog-devel Digest