chouette-core/db, branch 5486-fix-react-warnings Chouette manage transport static data Update branch according to master 2018-02-07T15:46:38+00:00 cedricnjanga 2018-02-07T15:46:38+00:00 3334b12153f0d24a95b1198742fd0da2444223fe 






Refs #5682; Add application_days field to calendars
2018-02-07T15:24:32+00:00

Zog

2018-01-24T06:28:57+00:00

53009774ec18387a30689a25ae286ba76e0e15d8












Refs #5750 @1h; Add a "kind" attribute to StopAreas
2018-02-07T15:24:32+00:00

Zog

2018-01-26T15:17:22+00:00

cb1c6c42cf0f053d52a08cb8ccdbb70a142ec5ad

This determines if the StopArea is commercial or not
The useless fields are hidden in the form for the non-commercials ones





This determines if the StopArea is commercial or not
The useless fields are hidden in the form for the non-commercials ones







First draft for including calendars into workgroup for having appropriate scoping
2018-02-07T15:19:49+00:00

cedricnjanga

2018-01-24T06:46:16+00:00

308bf4338b3e79016e353555ee3677c917c71805












Set all existing `StopArea`s with nil `kind`s to `:commercial`
2018-02-07T15:17:00+00:00

Teddy Wing

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

93ece87723191a33a830650cfa8c6cbc75470279

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







Refs #5750 @1h; Add a "kind" attribute to StopAreas
2018-02-07T15:01:03+00:00

Zog

2018-01-26T15:17:22+00:00

849f552b796118b4ab7cabbbda8b9ce1b5d4bc54

This determines if the StopArea is commercial or not
The useless fields are hidden in the form for the non-commercials ones





This determines if the StopArea is commercial or not
The useless fields are hidden in the form for the non-commercials ones







Update calendar form_simple according to workgroup
2018-02-06T19:21:58+00:00

cedricnjanga

2018-02-06T18:43:59+00:00

ad7dfea7f280cdf0727dd3471a1f26db4197c394












First draft for including calendars into workgroup for having appropriate scoping
2018-02-06T19:21:37+00:00

cedricnjanga

2018-01-24T06:46:16+00:00

b4ea175349adaffe4c797c7077865b2dd1c0fc20












Refs #5750 @1h; Add a "kind" attribute to StopAreas
2018-02-06T19:21:37+00:00

Zog

2018-01-26T15:17:22+00:00

3fa91b720184edfe319081230decc13f695072b2

This determines if the StopArea is commercial or not
The useless fields are hidden in the form for the non-commercials ones





This determines if the StopArea is commercial or not
The useless fields are hidden in the form for the non-commercials ones







First draft for including calendars into workgroup for having appropriate scoping
2018-02-06T19:12:34+00:00

cedricnjanga

2018-01-24T06:46:16+00:00

74d28c64603c70dc5463c9bc72954b886760f6cd