Bind subdomain with SQL

Question

0.00/5 (No votes)

See more:

Hi developers,

I would like to create a webApp with a general domain ex. mainApp.com
and multiple subdomains for each client ex. sub1.mainApp.com, sub2.mainApp.com etc.

What is the best way to bind each subdomain with the MySql.

I am thinking to create a unique id for each subdomain.

For example:

1. track the subdomain.
2. generate a unique id for the database ex. select * from "table" where client_id = "1231". (subdomain)

Is this the correct way;

What I have tried:

I am in process for the the DB design

Posted 13-Nov-21 20:23pm

Vangelis Chasiotis

Updated 13-Nov-21 21:40pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2021-11-13T21:40:00

This highly depends on the data and the regulations you need to comply with. For example in some cases it's not enough to separate the data only by some id in a single database. In order to keep the data complete separate you may need to utilize completely separate databases.

In other scenarios a single database may be sufficient but you may need to create row level security one way or another. Also note that depending on the situation, it may not be enough to separate the data from the user point of view, you may also need to separate the data from admin/developer point of view.

If single database would be sufficient I'd recommend getting familiar with views and stored procedures which are basic tools to achieve row level permissions. Also pay close attention to the native permission management MySql has to offer to ensure that permissions are controlled reliably.