2 questions: unique properties + history

Dear Roundup users,

I have read the guide "Customising Roundup", and I started to build by
own tracker. I ran into two questions:

1. Is it possible to tell Roundup to enforce the uniqueness of more
than one property of a class?
I guess that Roundup verifies that the key property is unique
(this seems to be an analogoue of PRIMARY KEY in rdbms). Can we set a
unique attribute for some other properties, e.g. setunique(prop), like
the UNIQUE constraint in rdbms? (In some use cases, there are more than
one IDs, one for internal usage, and an other one for being the part of
a larger system.)
Or these types of checks must be done in an auditor?

2. I will have to do some statistics on my tracker in the future. To
this end, I have to carefully journal everything. By inspecting
Roundup's source code and the database created by Roundup, I think
Roundup journals every change on items (unless do_journal='no' is set),
even if a String property is changed. 
And the history format is described in the journal method of Class
class in roundup.hyperdb:

The history "list contains tuples of the form
(date, tag, action, params)",

where the action parameter can be (according to addjournal method of
Database class): 'set', 'create', 'link'/'unlink', or
'retired'/'restored'.

And I can figure out from the impementation of context/history, how to
process the history entries. (Unfortunately, context/journal is not
implemented. :)

Am I right?

+1. My lame bonus question:
Can I change the initial id (of issues) from 1 to an other number? :)
(To easily "continue" the numberings of an old issue tracker.)

Regards,
Gábor Nagy 








_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users