FUDforum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » FUDforum Development » Bug Reports » BUGs: LIMIT clause in postgresql
Show: Today's Messages :: Polls :: Message Navigator
Return to the default flat view Create a new topic Submit Reply
Re: BUGs: LIMIT clause in postgresql [message #8041 is a reply to message #8040] Thu, 09 January 2003 05:17 Go to previous messageGo to previous message
laser is currently offline  laser   China
Messages: 9
Registered: January 2003
Karma:
Junior Member
sorry, my fault, I should make it more clearly.
Here is detail.

I'm not so familiar with FUDforum, (I'm using 2.3.6 now), so please forgive my ignorance about FUDforum's detail.

When I installed, there only one file need: install.php.
It's wonderfully easy for us to install and configure. Great job!

I think it's install.php who generate all those code need to run
the forum, that is, the install.php is like a self-zipped archinve, right? But it's plain text, except a few bytes at the header field. I can use emacs to edit it.

When I first meet those LIMIT #,# clause problem, I greped all occurence of LIMIT and change all those files --- lots of them,
you know, may be a few dozen files need to be change. And it's
tiresome work. So I want to change install.php directly, then all
the files it generate would be OK to use, it's much more easy.
and won't be so error prone. So I try to change install.php, fix those extra comma and those LIMIT clause directly, then I got checksum error while installing it. then I continue to revise it,
comment out those md5() check for I'm sure the file is correct,
but still get install error finally, take a look at index.php after install, it was obviously miss some bytes because those changes I made. so I give up, and reinstall using original install.php (make a little change: delete the extra ',' but added a blank space ' ' to complement the byte), install, and
change those files again.

So I want to know how to fix my problem at "root", and make my
life more easy, and maybe I can provide a patch for postgresql
too.

thanks.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: bad default sql table prefix
Next Topic: 2.3.6 listing bug?
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Nov 29 22:40:12 GMT 2024

Total time taken to generate the page: 0.05519 seconds