Add Singleton Support

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.

[therealmitchconnors]

Implement QuerySingle methods and classes to support singleton
operations.

[therealmitchconnors]

Fixes #14

[tuomur]

Thanks for looking into this. Copying all of query.py just for some small changes seems a bit too excessive. You could likely implement this in a more leaner way with a Entity subclass that returns the singleton's URL when queried. Metadata also would need to properly construct the Singleton classes.

[therealmitchconnors]

I have trimmed out all the functions that were not used by singletons (filter, top, skip, etc). I see that I could trim a bit more from the get_options and new_query functions where they relate to those operators to reduce the size of this feature, but I think the rest of the class is being used...

With regard to the Entity subclass, what would that look like? With reference to the TripPin service, we would construct the Person entity, as well as a PersonSingle sublcass? How would we execute the query? Would the query return a Person entity or a PersonSingle entity?

Thanks!

[tuomur]

I had a look at Singletons too, and ended up rewriting some of the EntitySet handling. Check it out at 9bfff03 (new branch)

I tested this with the TripPin URL you mentioned.

[therealmitchconnors]

That looks promising. How would you go about using this model from the Service class? Something like service.query(Customer, 'CustomerSingleton')?

[tuomur]

Sorry, forgot to mention the usage changes :)

Service.entities now contains the EntitySets with their original names (People, NewComePeople, Me) and those classes can be queried as usual. So for example:

Service=ODataService('http://services.odata.org/TripPinRESTierService/', reflect_entities=True)
Me=Service.entities['Me']
me=Service.query(Me).first()

[therealmitchconnors]

I see, so singletons are effectively just an array of one?

[tuomur]

I merged my singleton branch to master.

[tpow]

This pull request can be closed. @tuomur implemented singleton support and merged it to master.