Reply To: Quick reservations for recurrent clients

It’s not that this wasn’t the first idea. But in fact the plugin slows down a site in a palpable degree and every more information’s to save will higher this factor. Of course this function could be optional so everyone can decide if it’s worth it, but even then the impact is to low for the amount of data in the database. It’s an additional entry per reservation.
What could it change? That the logged in user automatically can edit his reservations on the edit site?
To let them edit it in backend as other plugins do is not really user friendly, is it?
That’s not enough. There’re way more better functions I haven’t made for the reason of to much database usage.
Or did I forgot an important argument for it?