World: r3wp

Thanks to the new CSS, the look is now consistent across Chrome / 
FF / IE7, but I gave up on trying to hack the CSS to make IE8 render 
pages as the others. The time spent in making all browser render 
the same way is quite insane.

Hey Doc, is this picture of CureCode schema still current ?
http://softinnov.org/dl/DB-schema.png

nice, what's this "drawn" in?

Doc said 27-Aug-2008 in this group "Microsoft Visio"

Nope, the schema was changed a little for R3 specific needs.

I didn't had the time yet to update the picture.

I'm interested in the "logs" table. It records changes to tickets 
once they are created, right?

Right, it records every event for each ticket (including creation).

If a new project is created, does that go into the logs table?

(as an example).

In the "tickets" table, there are several foreign key fields of INT(8) 
which link to tables with ids of INT(16), eg. severities.
Is that just an oversight?

New project => not logged, only tickets info are logged.

That's a typo, it should be INT(16).

Ok, that makes sense. So does the "field" field of the logs table 
tell which field of the tickets table was changed?

If so, then when several fields of a ticket are changed at once, 
does that generate several log entries in the logs table?

That is what the log at the bottom of the ticket shows, Anton.

Yes, each field changed generates a new log entry.

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.