Re: problem with schema changes

Thread: Re: problem with schema changes

Search this list only Search all lists
Re: problem with schema changes
	2007-01-24 22:59:15
Sorry for the belated response - just noticed this message was marked un(read == responded). On 16/01/2007, at 4:59 AM, Toni Mueller wrote: > * (At least) For existing tickets, most of the new fields are > undefined. Consequently, the attempt to calculate with them yields > an error. Now I thought I'd just catch that and set those fields to > something like "0", this doesn't seem to work because somehow these > changes aren't propagated to the database, and also not read back. > Therefore, the usual attempt at calculating with this stuff doesn't > work ("... has no attribute _value"). How did you set the "catch that and set those fields"? Was there a database commit at the end of the operation? > * The second problem is that I don't know how to set things like the > issue number programmatically (the user should have no way to > manually fiddle with that), or how to preset input fields with > default values (eg. date worked on = last working day). Setting the id may be done through the Python API using the Database.setid(classname, id) call. The next id allocated will be that id +1. Richard ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Roundup-users mailing list Roundup-userslists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/roundup-users