Mads Odgaard

Here is how I am doing it currently, maybe some inspiration: https://gist.github.com/madsodgaard/dd46221819c25847a6006a1139c78ebb This allows me to do this: ```swift extension Application { var factories: Factories { .init(app: self) } class...

@0xTim @miroslavkovac is right in that is not supported natively by SQL-Kit. I added some extensions to my code to help with using Fluent models in SQLKit code > **This...

@gwynne I am using it to have SQL as a value instead of having to drop down to `SQLKit`. Would you prefer having explicit methods for SQL instead? I mean...

Well done noticing this! I guess an issue is that to provide the same functionality we could end up just doing `n` amount of individual queries instead of utilizing database...

@gregcotten This happens because the actual `try await self.save()` does not fail. It is the wrapping transaction that fails, and therefore just causes a `ROLLBACK` and propagates the error up...

Thanks for your input! I am not sure if we want multiple email tokens per user to exist, so I think the `unique` constraint is fine. However, all previous tokens...

Currently, the example does not have the abstraction for email functionality, PR's are welcome though. Mailgun has a pretty good free tier for testing in my opinion, but you are...

@JetForMe It's only `Application.Repositories` that is instantiated, that type is just a helper type for accessing the actual factory methods for repositories. The actual factory methods/closures are stored in `app.storage`...

@lllyasviel Would be great to have this feature available! Any pointers on how we would implement this?