Re: Problem with moving a projects contents to another project

Cristian Rodriguez R. wrote:
> Gregory T Pelle escribió:
>> Hello,
>>
>> We are just starting out using Flyspray (0.9.9 beta 2).  After setting 
>> up some projects, we decided to reorganize (move some of the projects to 
>> categories under a "master" project) and have broken the database a 
>> couple times.  (I have fixed the issue by modifying the data in the 
>> database, but this is a fault prone procedure that I would like to avoid.)
> 
> in some cases, sadly you can get inconsistences yes, this is because
> transactions are currenlty not implemented the way they should be, or
> the driver you are using simple do not support them. I hope we can
> correct this behaviuor for 1.0 in all cases where transactions are
> posible to use.
> 
> anyway to actually protect you a lilte against possible inconsistences,
> if you are using PHP5 set dbtype = "mysqli", in PHP4 and mysql > 3.23
> set dbtype="mysqlt" in flyspray.conf.php.

I will set dbtype = "mysqli" (we are running PHP5).

> 
> 
> 
> 
>> Before 0.9.9 beta 2 we were not given an error message, but since beta 2 
>> we have received the following error message:
>>
>> Query {UPDATE `flyspray_groups` SET project_id = ? WHERE project_id =
>> ?} with params {10, 4} Failed! (Duplicate entry 'Project Managers-10'
>> for key 2)
>>
>> on a otherwise blank page.
> 
> explicit errors are much better than a blank page ;) flyspray currently
> is not afraid to crash ;-)
> 
>> As the error message states, we have a "Project Managers" category in 
>> each project (it is the first thing we setup before using the project).
>>
>> Is this a bug that I should submit a bug report for, or do we need to 
>> modify our procedures for moving a project's tasks to another project.
>>
>>
> 
> hrmmm... Im flagging this email with red label , and i 'll check the
> cause of this error later..hrmm..but  this does **not** seem to be a bug
> in Backend::delete_project... ;)
> 
> 
> if you a handy sample data to test, open a bug report in our BTS please ;-)
> 

I do not have any handy sample data at the moment.  I will try to 
replicate the problem in a test database when I get a minute.

Part of the problem might be how we are setting up our projects.  Every 
project has a "Project Managers" group.  When we move one project to 
another it looks like the groups are migrated (which causes the 
duplicate entry error) which causes the move to stop in the middle of 
its database modifications...causing the destination project to stop 
displaying.  Hope that description is not too confusing. ;)

> 
> 
> _______________________________________________
> flyspray mailing list
> flyspray@xxxxxxxxxxxxxx
> http://lists.rocks.cc/listinfo.cgi/flyspray-rocks.cc

Thanks.

_______________________________________________
flyspray mailing list
flyspray@xxxxxxxxxxxxxx
http://lists.rocks.cc/listinfo.cgi/flyspray-rocks.cc