| # |
Mar 28th 2019, 16:18 |
 val |
@neon1024 the use case is when each customer has its own database, the schemas are identical for each customer and cake app needs to retrieve data from multiple databases (from identical table of the customer database). Or simply to switch from once customer database to another. Creating new connections is too expensive. |
| # |
Mar 28th 2019, 16:11 |
birdy247 |
Can an entity be tested against a validator without patching |
| # |
Mar 28th 2019, 16:06 |
val |
too bad :( |
| # |
Mar 28th 2019, 16:00 |
neon1024 |
I would think that the schema is a direct map of your database, which will have a connection. So I’d say no, there isn’t. You’d have to create a new connection |
| # |
Mar 28th 2019, 16:00 |
ricksaccous |
but you can do it at run time |
| # |
Mar 28th 2019, 16:00 |
ricksaccous |
you still have to create a new connection |
| # |
Mar 28th 2019, 16:00 |
ricksaccous |
@val https://book.cakephp.org/3.0/en/orm/database-basics.html#creating-connections-at-runtime |
| # |
Mar 28th 2019, 15:56 |
val |
Hi, is there a quick way in cake 3.x to switch to a different database schema without creating a new database connection? |
| # |
Mar 28th 2019, 15:37 |
ricksaccous |
and conditional validation is not even that bad |
| # |
Mar 28th 2019, 15:37 |
ricksaccous |
the only advantage i get from this is not having to write conditional validation |
| # |
Mar 28th 2019, 15:31 |
ricksaccous |
hehe |
| # |
Mar 28th 2019, 15:31 |
josbeir |
the guy who invented that... oy |
| # |
Mar 28th 2019, 15:31 |
josbeir |
yeah, dont overthink something as lame as addresses |
| # |
Mar 28th 2019, 15:31 |
cnizzardini |
<- big fan of meta_data |
| # |
Mar 28th 2019, 15:31 |
ricksaccous |
whatever that's called |
| # |
Mar 28th 2019, 15:31 |
ricksaccous |
i mean not normalizing, making generic columns |
| # |
Mar 28th 2019, 15:31 |
ricksaccous |
this is an unessecary pain |
| # |
Mar 28th 2019, 15:31 |
josbeir |
still, if you use it as metadata you wouldn't need those fancy sql functions and mange that stuff by your app |
| # |
Mar 28th 2019, 15:31 |
ricksaccous |
honestly after doing it this way i think normalizing in one big table is the way to go |
| # |
Mar 28th 2019, 15:30 |
neon1024 |
..amd query support too! :slightly_smiling_face: |
| # |
Mar 28th 2019, 15:30 |
josbeir |
mysql 5.7+ has decent json supprot :slightly_smiling_face: |
| # |
Mar 28th 2019, 15:30 |
neon1024 |
MySQL 5.7 :slightly_smiling_face: |
| # |
Mar 28th 2019, 15:30 |
cnizzardini |
not sure about maria/mysql |
| # |
Mar 28th 2019, 15:30 |
cnizzardini |
you can actually query on it there |
| # |
Mar 28th 2019, 15:30 |
cnizzardini |
i think PG has better support for json datatype |
| # |
Mar 28th 2019, 15:29 |
neon1024 |
Let me check |
| # |
Mar 28th 2019, 15:29 |
neon1024 |
Maybe we’re on MySQL, we did change recently |
| # |
Mar 28th 2019, 15:29 |
ricksaccous |
ok |
| # |
Mar 28th 2019, 15:29 |
ricksaccous |
hehe |
| # |
Mar 28th 2019, 15:29 |
josbeir |
yes |
| # |
Mar 28th 2019, 15:29 |
ricksaccous |
i am so behind on field types in dbs |
| # |
Mar 28th 2019, 15:29 |
ricksaccous |
oh, does that have json fields? |
| # |
Mar 28th 2019, 15:29 |
neon1024 |
Maria |
| # |
Mar 28th 2019, 15:29 |
ricksaccous |
@neon1024 do you use postegres? |
| # |
Mar 28th 2019, 15:29 |
josbeir |
1 addresses table, put common fields in there as field, put the rest in a json field |
| # |
Mar 28th 2019, 15:29 |
neon1024 |
You could also write an address data type and have the address json marshall into objects |
| # |
Mar 28th 2019, 15:29 |
cnizzardini |
So I would just use the 2 or 3 char ISO code for storing country since it fits in a char |
| # |
Mar 28th 2019, 15:28 |
cnizzardini |
But I am not a fan of high normalization |
| # |
Mar 28th 2019, 15:28 |
cnizzardini |
You could normalize the country_id |
| # |
Mar 28th 2019, 15:28 |
neon1024 |
Otherwise I’d have gone for a single table with generic columns |
| # |
Mar 28th 2019, 15:28 |
cnizzardini |
Honestly I would just do a single address table for all |