chouette-core, branch 5416_checksum_attribute--rb201802071702 Chouette manage transport static data Refactoring spec checksum support 2018-02-08T10:26:52+00:00 Xinhui 2018-01-09T13:46:40+00:00 f3769c9d9fa0d4bf3c620a9c95e0c7533da9801c Refs #5416 
Refs #5416
Refactoring use subject as factory 2018-02-07T16:09:22+00:00 Xinhui 2018-01-05T15:43:37+00:00 31b7b91b46d2e8f740d2cfd493836219f5a4f42d Refs #5416 
Refs #5416
Edit checksum stop_points attributes for route 2018-02-07T16:06:33+00:00 Xinhui 2018-01-05T15:28:28+00:00 8a5898177d9a793e791a7e1dcb3162f8bf11aecf Refs #5416 
Refs #5416
Edit support of list attributes 2018-02-07T16:02:28+00:00 Xinhui 2018-01-05T15:26:38+00:00 135637edcef986f80d024b8bdbb14b33477caf7f Refs #5416 
Refs #5416
Add workgroup to erd diagrams 2018-02-07T15:38:18+00:00 Luc Donnet 2018-02-07T15:38:06+00:00 e07ef0eb9dac728ee5033b42c318692e2368b897 






Update stif-reflex-api gem. Refs #5869
2018-02-07T14:30:34+00:00

Alban Peignier

2018-02-07T14:30:34+00:00

7c0aee14eea2c560c1645dd49b54f1027ff8827c












Begin workbench output show refactoring to use stif guidelines
2018-02-07T10:34:49+00:00

Luc Donnet

2018-02-01T14:10:51+00:00

274cbdc6dce4164da61902f216d8cece2ce52c5e












Merge pull request #281 from af83/5817-referential-vehicle-journeys-index--fix-StopArea-kind-a
2018-02-07T09:03:36+00:00

Luc Donnet

2018-02-07T09:03:36+00:00

de6ef9294f7a1890d6f9de479e965d571233a96e

5817 referential vehicle journeys index  fix stop area kind a




5817 referential vehicle journeys index  fix stop area kind a






Set all existing `StopArea`s with nil `kind`s to `:commercial`
2018-02-06T13:47:31+00:00

Teddy Wing

2018-02-02T17:14:03+00:00

7d24256844e33bcb7875076a4bcfae22dd308009

The other migration for this in
`db/migrate/20180126134944_add_kind_to_stop_areas.rb` didn't handle
`kind IS NULL`. Since all the `kind`s were initialised to NULL when the
column was created, the `where` query didn't select any stop areas
because it was looking for those with some varchar value, and thus it
wasn't able to update any.

This ensures our existing records all have a `kind` in case we end up
using the field in a template at some point and our old data bugs out.

Refs #5817





The other migration for this in
`db/migrate/20180126134944_add_kind_to_stop_areas.rb` didn't handle
`kind IS NULL`. Since all the `kind`s were initialised to NULL when the
column was created, the `where` query didn't select any stop areas
because it was looking for those with some varchar value, and thus it
wasn't able to update any.

This ensures our existing records all have a `kind` in case we end up
using the field in a template at some point and our old data bugs out.

Refs #5817







Revert "Prevent problem with StopArea#kind. Refs #5817"
2018-02-06T13:47:31+00:00

Teddy Wing

2018-02-02T16:57:01+00:00

2913e072467ca0f9f93186e39e42e637b3e33152

This reverts commit c2bc391ee91cac70e726d188be97dd2323df0df2.

Thanks to 76abdbd66c16e6e1233685a5fa28a42cba5580d9, this temporary fix
can be reverted. We don't actually need `kind` selected here, it was
only added to appease the auto-initialisation of `kind` in `StopArea`.
Now that we don't set a default value for `kind` on initialisation, we
can remove it from this `select`.





This reverts commit c2bc391ee91cac70e726d188be97dd2323df0df2.

Thanks to 76abdbd66c16e6e1233685a5fa28a42cba5580d9, this temporary fix
can be reverted. We don't actually need `kind` selected here, it was
only added to appease the auto-initialisation of `kind` in `StopArea`.
Now that we don't set a default value for `kind` on initialisation, we
can remove it from this `select`.