every post has id 1

[GoogleCodeExporter]

Is it just me or is the db writer just generating a post id of 1 for every 
post? This really fucked shit up. so I have already made a workaround. I have 
not committed it because I am wondering how a non-isolated issue like this 
would make it into trunk (it's a simple fix)...

Original issue reported on code.google.com by hackmiester on 18 Jan 2011 at 4:44

[GoogleCodeExporter]

3 things.

1) I've never had this issue in any of the test installs I've ever set up nor 
on the two sites I know of that use this software.

2) Stop using /trunk/, it's from 2008.

3) Show me what you've got.  I'd love a reason to remember the software exists 
and fix the three bugs I've been meaning to fix since 2009.

No joke, though.  If you can give me what you've got I can try to figure out 
where the issue is, what might be causing it, implement your fix in trunk (yes, 
I know I said not to use trunk, but aside from a few issues, trunk is more 
functional than the current branch, which has technically needed to be merged 
into trunk on several occasions now but I just never did it), and maybe I will 
be motivated to stop playing minecraft or pokemon for one god damned minute and 
do some coding.

Original comment by TaQS...@gmail.com on 18 Jan 2011 at 8:42

• Added labels: Component-Logic, Component-Persistence, DBI-MySQL, Type-Defect

[GoogleCodeExporter]

1. I assume that's why I shouldn't have used trunk.
2. I blindly checked out trunk and haven't looked at anything else about the 
project. Whoops. Hey, it's better than people who make new installations of 
Futallaby.
3. Not sure what you mean about giving you what I've got, but what I discovered 
was in dbi/MySQL.php on line 574 or so, the line was:
$this->myresult($sql,0,"globalid");
Of course we are trying to return the globalid, so really what was meant was 
this:
$globalid = $this->myresult($sql,0,"globalid");

Original comment by hackmiester on 18 Jan 2011 at 4:18

[GoogleCodeExporter]

Maybe I was a bit rude about the situation.  As of right now, the trunk build 
is probably less buggy than what is in branch (the june 11 SQLite build, which 
isn't really about SQLite, but restructured a ton of the code and added SQLite 
support... branched I believe 2008, as opposed to march 2008 like trunk).  It's 
fine to use, if it functions for you.

I'll check out where that bug is and see about patching it and putting it in 
trunk.  As far as the SQLite build goes, because the dbi was rewritten it's 
probably gone, but there are a few other issues with that build that we kind of 
stopped working on after anonib pulled the plug on us (other reasons, too!).

This is now functioning as my blog.

Original comment by TaQS...@gmail.com on 18 Jan 2011 at 4:33

• Changed state: Started

[GoogleCodeExporter]

I'm willing to be somewhat committed (hurrrrrr) to fixing issues enough to have 
a working board, if you give me commit ability.

Original comment by hackmiester on 18 Jan 2011 at 5:18

[GoogleCodeExporter]

Yeah, I can do that as soon as I get to a computer.

Original comment by TaQS...@gmail.com on 18 Jan 2011 at 7:56

[GoogleCodeExporter]

I added you a while ago, so I guess just go ahead and add it in and... actually 
I'm not sure what perms you have, so maybe you can't mark this as fixed, but if 
you can't, I'll try to fix it.

Original comment by TaQS...@gmail.com on 20 Jan 2011 at 3:47

[GoogleCodeExporter]

Original comment by TaQS...@gmail.com on 4 Feb 2011 at 12:10

• Added labels: Milestone-0.3.0

[GoogleCodeExporter]

Whoa, sorry! Never noticed you added me, not sure where the notifications 
started going if not to my inbox. I'll check-in something ASAP.

Original comment by hackmiester on 4 Feb 2011 at 1:06

[GoogleCodeExporter]

Appears to be fixed.

Original comment by hackmiester on 5 Feb 2011 at 8:47

• Changed state: Fixed