Closed (fixed)
Project:
Remote Entity API
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
11 Jun 2014 at 21:50 UTC
Updated:
26 Jun 2014 at 12:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
colanSee attached.
Comment #2
joachim commentedI think with my usage of the module, I always need to define table info, but by the sounds of it you don't. So makes sense. Committed, thanks!
BTW, I'm curious about what type of remote data you're using this with!
Comment #4
colanI'm using a REST API as the back-end data store so there are actually no remote tables that I need to worry about. I didn't really understand what the point of defining a remote table if the source is over Web services. Maybe that's the problem. Should I not be defining a "remote base table" in hook_entity_info()?
Comment #5
joachim commented> Should I not be defining a "remote base table" in hook_entity_info()?
Yes, you should.
The extra table info in hook_remote_entity_query_table_info() came about because it turned out that with MS Dynamics I needed tons of extra data about field types and relationships and so on to make properly-formed queries and remote saves. It felt like too much to dump all that into hook_entity_info(), as that's loaded just about every page load.
I think Remote Entity is going to need a bit of a rethink for a 2.0 version because there are quite a few decisions that I made when backed into a corner and things that got tacked on not very elegantly, but that's not going to be until the end of the current phase of the project I use it on -- probably in the late autumn.
Comment #6
colanGood to know. I just made it the same as the "base table" as in the Programming Drupal 7 Entities example, but I don't think it's being used anywhere in my case.