Log message #4151909

# At Username Text
# Jun 15th 2018, 19:15 lorenzo @itmpls I also vote for single db for all tenants
# Jun 15th 2018, 19:14 tewinkel My main table is organisation. Every organisation has a list of delivery-actions, which consist of a combination of fruit, driver and supermarket.
# Jun 15th 2018, 19:12 tewinkel Yes sorry, dont know how to format my question properly
# Jun 15th 2018, 19:12 mikesmoniker pastebin that?
# Jun 15th 2018, 19:09 tewinkel test\ntest
# Jun 15th 2018, 19:07 tewinkel ruits. I want to see the names
# Jun 15th 2018, 19:07 tewinkel I have these tables: fruits ------- id name drivers ------- id name supermarkets ------------- id name deliveries ------------- fruit_id driver_id supermarket_id organisation_id organisations -------------- id name .... many fields --- I have baken the source for my application. If I take a look at a single organisation, i can see all deliveries belonging to this organisation. But the table of deliveries contains only the
# Jun 15th 2018, 19:07 itmpls ask away
# Jun 15th 2018, 19:06 tewinkel Hello! I need some help concerning table joins. Are there any experts round here?
# Jun 15th 2018, 18:32 itmpls probably going with a single db for simplicity and i'm not gonna have hundreds of tenants or anything
# Jun 15th 2018, 18:29 admad @mikesmoniker very insightful response :+1:
# Jun 15th 2018, 18:27 itmpls thank you @mikesmoniker
# Jun 15th 2018, 18:20 itmpls ah ok
# Jun 15th 2018, 18:17 mikesmoniker Final thought: if you do go with multiple DBs, please research how to properly encrypt their individual credentials. Don’t just throw them in a table somewhere in the clear. That seems to occur in the wild way more than it should.
# Jun 15th 2018, 18:16 mikesmoniker But I wouldn’t necessarily advise designing _for_ those kinds of horrible cases. Presumably you have good design, tests, etc. to mitigate those risks.
# Jun 15th 2018, 18:16 mikesmoniker The times I did multi-DB didn’t really fall under those scenarios, but the benefits included things like a breach/security issue (in theory) only put one customer at-risk, it was virtually impossible for a bug to cause one customer to see another’s data, and if we screwed something up big time we could roll back a single customer’s DB without having to stitch together data.
# Jun 15th 2018, 18:14 mikesmoniker My advice is a single DB for all tenants unless you have a compelling reason not to (e.g. serious privacy/compliance concerns, scaling to millions of customers, etc.). It’s way simpler.
# Jun 15th 2018, 18:13 mikesmoniker A couple things to consider: would you pair a codebase with each db. (e.g. one instance of the app to many DBs, or one-to-one? The former makes DB migrations complicated.) Do you need to do complex cross-tenant reporting.
# Jun 15th 2018, 18:11 itmpls any recommendations specifically from experience?
# Jun 15th 2018, 18:11 itmpls gotcha. I was thinking a db per tenant honestly because the rollbacks and what not would be easier, but it might be a little bit more of a setup
# Jun 15th 2018, 18:10 mikesmoniker Nope, but the _how_ is pretty similar across all frameworks.
# Jun 15th 2018, 18:10 itmpls have you done it specific to cake though?
# Jun 15th 2018, 18:10 mikesmoniker I think there was also a full stack radio podcast episode about it somewhat recently, if I remember correctly.
# Jun 15th 2018, 18:09 mikesmoniker @itmpls Sure. I’ve worked on multi-tenant apps that did it both of the common ways. I’d hit the Google, as there is a lot written out there on the subject.
# Jun 15th 2018, 18:03 itmpls more specifically i suppose, has anyone delegated a db per client/tenant in a saas architecture? or not?
# Jun 15th 2018, 18:00 slackebot ~tell medes about anyone
# Jun 15th 2018, 18:00 slackebot Command sent from Slack by admad:
# Jun 15th 2018, 17:58 blackjccl Hi community
# Jun 15th 2018, 17:57 itmpls has anyone done any saas stuff?
# Jun 15th 2018, 16:38 camdenbassett @dereuromark Yes, thanks. I'll most likely put just put them in the webroot folder, but it's good to know I'd need to do some through-putting if I stored it somewhere else.
# Jun 15th 2018, 16:20 ngashpoll Thanks @dereuromark for clarifying that.
# Jun 15th 2018, 16:12 dereuromark camdenbassett: that depends if they may be public or not. the latter must NOT be in the webroot obviously, but served via some response through-putting from below the surface (e.g. stored in /files or sth)
# Jun 15th 2018, 16:01 camdenbassett Ah, thanks. It didn't look like there was a recommended folder, but I thought I'd just check. Thanks for the info
# Jun 15th 2018, 16:00 ngashpoll Hi @camdenbassett, there is no specific recommended folder to store files but you can add a folder under webroot to store files.
# Jun 15th 2018, 15:57 camdenbassett Hello everyone. Quick question, is there any recommended folder to store pdfs, mp3s, and other downloadable content in the CakePHP folder structure?
# Jun 15th 2018, 15:22 josbeir altho probably not strict enough...
# Jun 15th 2018, 15:21 josbeir => http://php.net/manual/en/migration71.new-features.php#migration71.new-features.iterable-pseudo-type
# Jun 15th 2018, 15:20 josbeir @dereuromark in 7.1 theres iterable pseudo type that can be used as typehint ?
# Jun 15th 2018, 15:04 josbeir File uploaded https://cakesf.slack.com/files/UAG1HNWKT/FB896HJSX/image.png / https://slack-files.com/T053DPNCM-FB896HJSX-4a7798b1e4
# Jun 15th 2018, 15:02 josbeir bit lame :P
# Jun 15th 2018, 15:02 josbeir @dereuromark i know but thats not convenient, for instance when i manipulate date in beforeMarshal i need to do getArrayCopy, manipulate, then loop trough the Hash::inserted array en reset the keys on the object