I'm currently doing some tests with exposing remote data/objects/entities as entities.

It actually works quite fine, thanks to EntityAPIController I can just override the query method. However, there is a hardcoded attempt to load the schema to deal with serialized fields in load()

I had to work around that by copy & pasting the load method and removing that stuff, would be nice if there would be a condition around it or another way to customize/override it without copying the whole thing.

I can provide a patch if you're ok with doing this.

PS: I do get some errors too from the default meta controller but I will have to override that anyway.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Title: Hardcoded base table references conflicts with remote entities » Ease implementing remote entities
Category: bug » task

Well, that is as currently the EntityAPIController is supposed to deal with entities stored in your DB. But I agree it shouldn't to make other use-case simple too, so I'd be happy if you can take care of that.

Ideally, we'd also provide some Views integration for those entities what basically should just be "efq_views". With the already in place data-selection based Views-integration (fields), that shouldn't be hard to do either.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed

ok, I've done so by adding a simple check for the 'base table' key.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.