World: r3wp

Thanks, it is clear to me, now.

Are the changes to the API? I'm downloading the bug list from the 
API, but the column order does not correspond to what is in the docs. 
Also the column order is not mentioned in the docs.

API hasn't changed. Do you have an example URL? I don't see any difference 
in column order. Btw, I've just released a fix for a bug in the type=ticket 
mode throwing an error if the 'fixedin field was none.

Looks like you were talking about the "user" column that don't appear 
in the docs? I need to update CureCode's wiki.

updating the docs might solve the problem, so I'll wait with further 
action until that is updated.

For CureCode users: do you guys think that a project-wide timeline 
page like the following one would be useful? http://www.sqlite.org/cvstrac/timeline

yes, I think that could be useful

Everyone responds to different stats and/or different presentations 
of them. So the more ways to view the data sets the better.

Yes, I think so Doc.

CureCode reports, we have 888 closed tickets for R3.0 - good number 
:-)

makes us all very happy 8-)8-)8-)

Curecode 099 is not available for download on curecode.org. Is that 
on purpose?

Is doc releasing updates to CC?

098 is available, but 099 is not

Perhaps doc should consider moving curecode's source to google.  
Certainly it has helped having Cheyenne there.

looks to me that curecode 098 is hardwired for the R3 bug list. there 
is a ton of references to R3 in it.

Ah, only the database name is r3bugs. I think it would be relatively 
easy to move into a config?

using install.r, I get the following error:

CureCode Installation...
...loading MySQL protocol
Script: "MySQL Protocol" (12-Jul-2008)
MySQL protocol loaded
...creating database
...database root Password: *******
connecting to: localhost
...access ok to database
...creating tables

** User Error: ERROR 1136 : Column count doesn't match value count 
at row 1
** Near: make error! info

what's the sql?

trying to figure that out now

INSERT INTO users VALUES (
	NULL,
	'admin',
	'EE10C315EBA2C75B403EA99136F5B48D',
	['default-:-curecode-:-org'],
	'00000000000000000000000000000000',
	NOW(),
	4,
	NOW()
);

is the one with the most inserts !

CREATE TABLE users (
	id		INT(16) 	 PRIMARY KEY AUTO_INCREMENT,
	login	VARCHAR(32)  NOT NULL,
	pasw	VARCHAR(32)  NOT NULL,
	email	VARCHAR(128) NOT NULL,
	vkey	VARCHAR(32)	 DEFAULT NULL,
	vdate	DATETIME 	 DEFAULT NULL,
	role	INT(8)  	 NOT NULL,
	deleted	BOOL		 NOT NULL,
	created	DATETIME 	 NOT NULL,
	modified DATETIME
);

yes, it's the one that fails. deleting it makes installation work

inserting 8 values but needs 9 values

possibly better to use column names than a values block.

null shouldn't be the first value

admin should be first as that corresponds to login

I presume you can't insert into a primary key auto_increment field

now (), 4, false, now(), now ()

I think you should be able to, otherwise you wouldn't be able to 
use VALUES on a table with a primary key

or whatever mysql uses for boolean

but I would prefer if column names were in the query. it's easier 
to read.

INSERT INTO users VALUES (
	'admin',
	'EE10C315EBA2C75B403EA99136F5B48D',
	['default-:-curecode-:-org'],
	'00000000000000000000000000000000',
	NOW(),
	4, false, 
	NOW(), NOW()
);

something like that ... I suspect

change the email of course

yes, standard RT syntax includes column names


{insert into users ( login, pasw, email, vkey, vdate, role, deleted, 
created, modified ) values (? ... etc ) }  admin EE... blah ...

INSERT INTO users SET
	login		= 'admin',
	pasw		= 'EE10C315EBA2C75B403EA99136F5B48D',
	email		= ['default-:-curecode-:-org'],
	vkey		= '00000000000000000000000000000000',
	vdate		= NOW(),
	role		= 4,
	created	= NOW();

This works.

Just missing the deleted column

and modified

there must be other places where users are added ...

not sure they are needed. now onto how to make curecode log into 
mysql

yeah ... redundant fields :)

one would think, there would be a login to the database somewhere 
in the code. can't find it though. there is one in some test files 
and in the installer.

it's cheyenne

it will be in the Cheyenne cfg

httpd.cfg

I see.

well, I'm guessing ...

I've added that now, but Cheyenne is just outputting things the browser 
won't understand.