Open rustd opened 9 years ago
// Any time an entity is added/ deleted/ updated
public static void TableTrigger1([TableTrigger("tablename")] MyPoco mypoco)
// Any time an entity with a specified rowkey/partitionkey is added/ deleted/ updated
public static void TableTrigger1([TableTrigger("tablename","pk","rk")] MyPoco mypoco)
The polling model could be based on Storage logs.
I think there's another permutation on the signature that could be made:
public static void TableTrigger1([TableTrigger("tablename")] TableEvent<MyPoco> myPocoTableEvent)
I think in some cases, I'm not going to know the partition ahead of time, but it is significant to how I'll handle the event, so that TableEvent
type could be used to offer desired metadata outside of any DTO/model.
No update on this? Having the polling mechanism for table trigger consolidated with blob trigger will avoid to poll twice for the same information...
It'd be nice to use this. I hope they revisit this and implement it.
Please provide details on how you'd expect the binding to work. In general, for all "it'd be awesome to have trigger/binding X" I'd like issues created to include lots of details on attribute model, polling model, etc.