Missing database normalization

Hi,

How come you only use one table for subscribers and subscriptions (#__osmembership_subscribers)? This make it harder to extend the program to support multiple subscriptions. Any plans to refactor that part?

Regards
Olle

Hi Olle

I must be honest that it was my mistake when I designed the extension few years ago. I tried to split it into two tables in the part without success, so I will have to stay with my mistake for now (for at least 6 months more as right now, I want to focus working on improving the extensions, the structure still work well for me although I don't really like it) (it will still work well for me, it is just not easy for you to customize the extension, I think)

However, I am not sure what you are trying to do ? It could still doable with the current database structure(just not easy if we were having two tables in this case)

If you plan to make extensive customization to the extension and having problem with the better database structure, you might have to switch to a different extension before it is too late (of course, I will refund the money you paid)

Sorry for any inconvenience cause by my past mistake

Regards,

Tuan

Hi,

Thanks for your answer!

The database design is not a big problem, it just raised my eyebrows.

We have quite specific requirements, where one subscriber should be able to have multiple subscriptions and also be able to upgrade any subscription. I was hoping this could be done without too much hassle, preferably using a plugin. I was thinking about using events to change the date of new subscriptions, making them run simultaneously. And customize the profile page, and so on. What do you think?

Regards
Olle

Olle Haerstedt wrote:
We have quite specific requirements, where one subscriber should be able to have multiple subscriptions and also be able to upgrade any subscription.

Hi Olle. We have an identical requirement. I've been having a look at the tables and I can't see any practical way to do this. Did you have any success?

Hi Tuan, is this functionality likely to be added any time soon?

Thanks
John