Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
09/02/10 10:39:54 (14 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
assigned
-
Property
Remaining Time
changed from
0.75
to
0.5
-
Property
Priority
changed from
minor
to
critical
-
Property
Milestone
changed from
Unscheduled
to
OMERO-Beta4.2.1
- Property Owner set to jmoore
-
|
initial
|
v2
|
|
| 1 | | Currently, all spec.xml entries mention `XAnnotationLinks` but don't specify how/when to delete annotations. |
| | 1 | Currently, all spec.xml entries mention `XAnnotationLinks` but don't specify how/when to delete annotations. The initial implementation will mark all annotations as "SOFT", meaning that if a delete is not possible, that it will return a warning, but not cancel the delete. |
| | 2 | |
| | 3 | Note: A PostgreSQL issue made this more complicated (and possibly costly) that one would think. If we don't want to search the entire DB for other possible links, it's necessary to create a SAVEPOINT before '''every''' delete, and either release or roll it back afterwards. |
| | 4 | |
| | 5 | See: |
| | 6 | * http://archives.postgresql.org/pgsql-jdbc/2006-04/msg00002.php |
| | 7 | * http://www.postgresql.org/docs/8.1/interactive/sql-release-savepoint.html |
| | 8 | * http://nathansnoggin.blogspot.com/2009/01/postgresql-transactions-and-error.html |
| | 9 | * http://www.jroller.com/sjivan/entry/odd_postgresql_transaction_behavior |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.13126 sec.)
