On 03/07/2020 16:21, Pedro Ferreira wrote:
> Hi,
>
> I was wondering if there's some way to create some sort of a "virtual"
> model which is not based on an actual table?
>
> Use case: I have a model (e.g. `Room`) which contains a `data` JSONB
> attribute/column which is supposed to store
OK, thanks a lot anyway! I was just wondering if there was already some
solution I could reuse.
Cheers,
Pedro
On 03.07.20 17:26, Mike Bayer wrote:
> I suppose. that seems really complicated. When we use the ORM, we're
> defining our domain model in terms of objects, then we define a
>
On Fri, Jul 3, 2020, at 9:21 AM, Pedro Ferreira wrote:
> Hi,
>
> I was wondering if there's some way to create some sort of a "virtual"
> model which is not based on an actual table?
>
> Use case: I have a model (e.g. `Room`) which contains a `data` JSONB
> attribute/column which is supposed to
Hi,
I was wondering if there's some way to create some sort of a "virtual"
model which is not based on an actual table?
Use case: I have a model (e.g. `Room`) which contains a `data` JSONB
attribute/column which is supposed to store plugin-specific data. I
would like plugin code to be able to
