Sorting in Project and Order Views

[kboek]

Introduce chronological (by “date” field) sorting functionality for orders within the project view and for music requests within the order view.

[kboek]

In order to enable sorting for table orders and table song_requests, the sort field must be an obligatory field - in other words: NOT NULL

For orders the sort field will be performance_date
For song_requests the sort field will be date_created - which we by default can set to NOW()

[kboek]

Steps to deploy to production (incomplete)
Events

• Edit field orders - Relationshop and set Sort Field to performance_date
• In the same edit, under Interface, review the Per Page value (no manual reorder when paging)

Orders

• Change field performance_date; disable "Allow NULL value"
• Edit field song_requests - Relationship and set Sort Field to date_created
• In the same edit, under Interface, review the Per Page value (no manual reorder when paging)

Song Requests

• Change field date_created in song_requests; disable "Allow NULL value" and set Default Value to NOW()

[kboek]

Currently getting this update when manually changing order of orders in event/projects

{
  "message": "update \"orders\" set \"event_id\" = $1, \"performance_date\" = $2, \"date_updated\" = $3, \"user_updated\" = $4 where \"id\" in ($5) - invalid input syntax for type date: \"1\"",
  "extensions": {
    "code": "INTERNAL_SERVER_ERROR"
  }
}

And when manually changing the order of song requests in an order

{
  "message": "update \"song_requests\" set \"date_created\" = $1, \"order_id\" = $2, \"date_updated\" = $3, \"user_updated\" = $4 where \"id\" in ($5) - invalid input syntax for type timestamp with time zone: \"1\"",
  "extensions": {
    "code": "INTERNAL_SERVER_ERROR"
  }
}