Handling the public 'Meteor.users', when different storage backends are used with Accounts

[mariobriggs]

The Accounts package exposes 'Meteor.users' which is a MongoCollection (and documented so). However this is problematic when storage backends other than Mongo are used

a - The query API is different across Mongo/CouchDB and say Postgres (SQL).
Is it possible introduce a API for Meteor.users that is agnostic to the storage backend ?

b - Different backend might choose to store 'users info' across mutiples 'tables' (SQL) vs one 'collection' (mongo). Thus even if expose Meteor.users as is ignoring point 'a' above, as an app or package developer interacting with 'Accounts', i need to know internal storage impl details like is this 1 table or 3 tables (for instance if interested in tracking logins/logouts, becuase i need to subscribe to changes of that specific table)

[mariobriggs]

@stubailo wanted to tag this as 'accounts', but i cant see the option to add labels to the issu