Albert Puigsech Galicia

I am not using Mongo but a SQL database, so I am not linked to that limitation. I a managing a set of objects that comes from an external entity...

Okay, I can agree that there it may be good to have an specific field that refers to the key with consistency on its name. Do you think it's possible...

Yes, I need it for POST specifically. This a non-working-code-yet that I am going to experiment with. Maybe it's an stupid solution, so comments are welcome :) ``` type FieldCopy...

I do ``` r.Use(FieldCopy{Source: "name", Target: "id"}) ``` And it works when I pass an empty "id" field, but not when it's not there.

> First of all, if you are _able_ to modify the database to have a separate ID column, either a unique ID (e.g. xid) or a unique random ID (e.g....

> @apuigsech You are seeing this error, because `id` needs to be present in order for those `resource.Items` to be created in the first place. I guess apart from the...

By the way, do you think that adding support to REST-layer for custom key field would be interesting? Something like; ``` user = schema.Schema{ KeyField: "email", // This is the...

The problem is that postgres (the db i am using) is not implementing any kind of ttl.

This is exactly the solution I am working on. The only problem is that I cannot meet the requirement of forbidding the direct edit of 'DeleteAt' (as I want it...

I am not sure which is the best way to approach that, but I think that having Computed fields may be very powerful in some cases.