Message8359
Thank you for letting me know.
> How do you expect setting default_value will change how the REST
> interface operates?
I'm currently working on integrating our roundup instance (that has been
around for close to 20 years) with an external service using the REST
API. After adding columns to the schema and setting the default_value
for these, values in these columns are still returned as null from the
REST API. This only happens for rows that are older than the
aforementioned schema changes.
My expectation here would be that the default value would be returned
instead of null. If not, one would have to duplicate the information
about any default values in both the roundup instance and all consumers
of the REST API.
From your perspective, would this be a feasible change somewhere down
the line? Is there some nuance here that I'm missing? |
|
Date |
User |
Action |
Args |
2025-03-10 11:59:22 | wilsj | set | messageid: <1741607962.41.0.647480101181.issue2550911@roundup-tracker.org> |
2025-03-10 11:59:22 | wilsj | set | recipients:
+ wilsj, rouilj, ThomasAH |
2025-03-10 11:59:22 | wilsj | link | issue2550911 messages |
2025-03-10 11:59:22 | wilsj | create | |
|