I (Julian Foad) wrote:
> I'm planning to change the order of NODES columns so that they're
> grouped more logically, like in my BASE_NODE overview comment. If I
> can, I'll do this before switching to NODES as the default, as it is
> almost impossible to do later.
Done in r1005102, r1005104, r1005106, r1005107.
- Julian
> Currently:
>
> wc_id 1
> local_relpath 2
> op_depth 3
> parent_relpath 4
> repos_id 5
> repos_path 6
> revision 7
> presence 8
> depth 9 -> 13
> moved_here 10 -> (9,
> moved_to 11 -> 10,
> kind 12 -> 11)
> changed_revision 13 -> (16,
> changed_date 14 -> 17,
> changed_author 15 -> 18)
> checksum 16 -> 14
> properties 17 -> 12
> translated_size 18 -> 19
> last_mod_time 19 -> 20
> dav_cache 20 -> 21
> symlink_target 21 -> 15
> file_external 22
>
> Wanted:
>
> # Indexing
> wc_id 1
> local_relpath 2
> op_depth 3
> parent_relpath 4
>
> # Node-Rev
> repos_id 5
> repos_path 6
> revision 7
>
> # Restructuring
> presence 8
> moved_here 9 <- (10,
> moved_to 10 <- 11,
>
> # Content
> kind 11 <- 12)
> properties 12 <- 17
> depth 13 <- 9
> checksum 14 <- 16
> symlink_target 15 <- 21
>
> # Last-Change
> changed_revision 16 <- (13,
> changed_date 17 <- 14,
> changed_author 18 <- 15)
>
> # Misc. cached data
> translated_size 19 <- 18
> last_mod_time 20 <- 19
> dav_cache 21 <- 20
> file_external 22
>
> Any comments?
>
> - Julian
Received on 2010-10-06 18:25:36 CEST