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:
-
12/03/12 11:56:30 (11 years ago)
- Author:
-
spli
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v2
|
v3
|
|
| 2 | 2 | |
| 3 | 3 | stop=0 is currently treated as a special case, eg: |
| 4 | | * |
| 5 | | * |
| 6 | | * |
| 7 | | * |
| | 4 | * read(start=0, stop=0) returns row 0 |
| | 5 | * read(start=i, stop=0) returns row i |
| | 6 | * read(start=i, stop=i) returns no rows |
| | 7 | * read(start=i, stop=i+n) returns rows[i..i+n-1] |
| 8 | 8 | |
| 9 | 9 | The apparent intention is to replicate the underlying behaviour of PyTables which uses stop=None to indicate one row should be returned. However, in OMERO.tables stop=0 is treated as stop=None which breaks the standard way of specifying Python ranges. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.14958 sec.)
