Hi Ethan,
> I really don't want to go down the rabbit hole of retaining optional
> backwards compatibility for every little feature we remove just because
> there might possibly me some badly configured user who is affected on
> upgrade. I'd prefer not to accept this patch until there's a more sp
Hi Ben,
The get_all_records_where functions are indeed not very well documented,
probably because the way to use them is a little awkward. I think we should at
some point introduce new APIs to selectively query the database and discourage
the use of get_all (because it does not scale). Currentl
From: Dominic Curran
Fix bug in commit 3249bb907a1dab9b0
Incorrectly assume that get_all_records_where() returned a list.
It infact returns a disctionary and the list iteratory needs to change
to account for this.
Thanks to Nicira for pointing this out.
NIC-454.
Signed-off-by: Rob Hoes
