Re: [Radiant] MySQL SystemStackError: stack level too deep:

2007-09-20 Thread Mark Kirby
On 20 Sep 2007, at 00:47, Daniel Sheppard wrote: The following will show how deep your ruby stack can go: ruby -e '$x=0;def r;$x+=1;r;end;r rescue puts $x'; That command doesn't work for me My system can go 5050 levels. Ruby relies on the system limit on the C stack to limit its own

Re: [Radiant] MySQL SystemStackError: stack level too deep:

2007-09-19 Thread John W. Long
Mark Kirby wrote: stack level too deep SystemStackError: stack level too deep: SELECT * FROM page_parts WHERE (page_parts.page_id = 6) AND (page_parts.`name` = 'extended') LIMIT 1 Any one have any ideas? Do tests run for you? -- John Long http://wiseheartdesign.com

[Radiant] MySQL SystemStackError: stack level too deep:

2007-09-19 Thread Mark Kirby
Hi, if i create a vanilla radiant app using the styled blog and an empty mysql database (though postgres displays the same problem) i get the following trace when i try to delete an article. Also when going to the front page each article body has stack level too deep SystemStackError:

Re: [Radiant] MySQL SystemStackError: stack level too deep:

2007-09-19 Thread Mark Kirby
On 19 Sep 2007, at 14:05, John W. Long wrote: Mark Kirby wrote: stack level too deep SystemStackError: stack level too deep: SELECT * FROM page_parts WHERE (page_parts.page_id = 6) AND (page_parts.`name` = 'extended') LIMIT 1 Any one have any ideas? Do tests run for you? The 1st block

Re: [Radiant] MySQL SystemStackError: stack level too deep:

2007-09-19 Thread Daniel Sheppard
stack level too deep SystemStackError: stack level too deep: SELECT * FROM page_parts WHERE (page_parts.page_id = 6) AND (page_parts.`name` = 'extended') LIMIT 1 Do you have any extensions installed? They could be breaking things. If not, It could actually be that the stack level is too