Skip to content
This repository has been archived by the owner on Jul 4, 2021. It is now read-only.

write and delete support #10

Open
snarfed opened this issue Dec 6, 2011 · 2 comments
Open

write and delete support #10

snarfed opened this issue Dec 6, 2011 · 2 comments

Comments

@snarfed
Copy link
Owner

snarfed commented Dec 6, 2011

Originally filed by heaven on 2011-11-12T07:25:04

publishing and deleting via POST/DELETE: https://developers.facebook.com/docs/reference/api/#publishing

@snarfed
Copy link
Owner Author

snarfed commented Dec 6, 2011

Updated by heaven on 2011-11-14T20:39:23

Original ticket set status to Accepted (we converted to open)

@snarfed
Copy link
Owner Author

snarfed commented Dec 6, 2011

Updated by heaven on 2011-11-15T01:31:09

this will take more effort than it might seem. the big stumbling block is the duplication of data between the graph_objects and graph_connections tables, which serve objects and connections respectively.

one approach would be to write a schema mapping from object to connection representations, and translate each POST into two INSERTs, one for each table. the schema mapping isn't difficult, but would be time intensive, similar to the unfinished work that went into graph_on_fql.py.

another, probably better, approach would be to unify the two tables, and serve connections from graph_objects. this would require basically the same schema mapping as above, but would get rid of the duplication, which would be much better. that's probably what we should do.

Title changed from 'write and delete support' to 'write and delete support'

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant