irmis-devel Mailing List for IRMIS
Status: Alpha
Brought to you by:
carcassi
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(2) |
Feb
(10) |
Mar
(5) |
Apr
(5) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
|
2
|
3
|
|
4
|
5
|
6
(1) |
7
|
8
|
9
|
10
|
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
|
25
|
26
|
27
|
28
(1) |
29
|
30
|
31
|
|
From: Carcassi, G. <car...@bn...> - 2009-10-28 20:26:39
|
Hi all, New release: https://sourceforge.net/projects/irmis/ <https://sourceforge.net/projects/irmis/> We started to implement support for cable types/functions/bundles/paths, which can be used to keep track of how cables are used and pulled across a site. We plan to develop and use these future to plan and capture the cable information for NSLS-II. There is a schema update script to create the tables, and part of it is already supported at the service and API level (all except the bundles and paths). I also reviewed more closely the GUI widget, which solves a few issues that would crop up from time to time. Full change log is available on Trac at: http://sourceforge.net/apps/trac/irmis/query?status=closed&group=compone nt&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col =component&col=version&milestone=3.0.12-alpha%20(r1115) Gabriele |
|
From: Carcassi, G. <car...@bn...> - 2009-10-06 16:04:06
|
Hi all, We are finalizing the schema that keeps track of where cable are pulled across the site, through trays partitions and all. The new addition will have a set of additional constraints that cannot be satisfied when upgrading. For example, each cable bundle that is being pulled will require to have the cable type associated with it: given that we previously did not have cable types either, there is no away to upgrade the database enforcing this requirement. In this case, what I would do is have two scripts: one that upgrades with the constraints turned off, and a separate script to turn on the constraints that one would run after the data is fixed. I am assuming, though, that no-one really populated that area of the database (cable_pull, cablepull__traysegment), given that there was very limited support. Therefore I will be preparing only one script that simply assumes no data is there. (Note that cables/conductor themselves are not affected) If you have populated data only from the GUI or from the Java API, you are guaranteed to not be affected. If you have no idea what I am talking about, you are most likely not affected either. If anybody did in fact put some data in, either through the service or through direct access to the db, please let me know and I'll prepare the extra scripts. Thanks! Gabriele |