Stevebenson223
Member
Hi all
This is as much a design problem as a technical problem.
I am building a simple membership app in Fabrik which is almost complete. But I have hit a problem in displaying members whose subscriptions have expired and have not been renewed. This is basically because of the design of my database, but I can't see an alternative design.
I have designed the database/app using three basic tables:
1) members: name, email, address, contact details, etc
2) membership type: membership plan, cost, expiry type (one year, never)
3) subscriptions: databasejoin to members table, databasejoin to membership type table
(there are other tables and fields, but these are the principle ones).
To me, this seems a logical and efficient design for the database. However, I need to show a list of members whose subscription has expired. I created this using subscriptions and it works, BUT it shows all expired subscriptions EVEN IF the member has now purchased a new subscription. Obviously, this is because it is looking at subscriptions and I need it to look at members. I feel I need to add a field to the members table to show a current subscription but I've not been able to find a way to do this.
I guess my questions are: is my database design basically correct and if so, is there a "standard" way to handle expired subs? There must be lots of people who have built similar apps?
Thanks to anyone who can point me in the right direction.
This is as much a design problem as a technical problem.
I am building a simple membership app in Fabrik which is almost complete. But I have hit a problem in displaying members whose subscriptions have expired and have not been renewed. This is basically because of the design of my database, but I can't see an alternative design.
I have designed the database/app using three basic tables:
1) members: name, email, address, contact details, etc
2) membership type: membership plan, cost, expiry type (one year, never)
3) subscriptions: databasejoin to members table, databasejoin to membership type table
(there are other tables and fields, but these are the principle ones).
To me, this seems a logical and efficient design for the database. However, I need to show a list of members whose subscription has expired. I created this using subscriptions and it works, BUT it shows all expired subscriptions EVEN IF the member has now purchased a new subscription. Obviously, this is because it is looking at subscriptions and I need it to look at members. I feel I need to add a field to the members table to show a current subscription but I've not been able to find a way to do this.
I guess my questions are: is my database design basically correct and if so, is there a "standard" way to handle expired subs? There must be lots of people who have built similar apps?
Thanks to anyone who can point me in the right direction.