Shard replied
Shard replied
So far I have separated into projects anything that feels like it makes sense to group together.
wkw replied
lets say u hv a database dbA
with 10 tables
if u create a project connecting to dbA
, u ll see those 10 tables
if u create another project connecting to dbA
, u ll see the same 10 tables
wkw replied
changes done in first project will be reflected in the second project as well - as u change sth in db
wkw replied
or your case s like u hv a db with 10 tables
first 5 tables r for project A
second t tables r for project B
?
Shard replied
I use nocodb projects as groups only. So for example I could have a project named Bills
with tables: electricity
water
heating
etc.
Shard replied
and for those two projects I donāt really care if they are on same db or not. As long as they are grouped separately in nocodb
Shard replied
or I mean I actually do care: as I donāt want to create 2 separate databases for these as it is simpler if they are on the same db
Shard replied
maybe Iām just approaching this bit weird. Maybe the ācorrectā way to do that in this case is to have a project named āMyNameā and then have all those 6 tables be under it.
wkw replied
the ideal approach would be separate them - then 2 projects connecting to 2 differenet dbs
wkw replied