| # |
Feb 1st 2018, 11:05 |
 ooskar1233 |
hm, thought that self-referencing would be user hasmany users |
| # |
Feb 1st 2018, 11:05 |
ooskar1233 |
:) |
| # |
Feb 1st 2018, 11:05 |
neon1024 |
Oh, ninja edit! |
| # |
Feb 1st 2018, 11:05 |
neon1024 |
Same thing :P |
| # |
Feb 1st 2018, 11:04 |
ooskar1233 |
not that self referencing, just two associations of different type to one talbe |
| # |
Feb 1st 2018, 11:04 |
ooskar1233 |
sure, but you don't mess around bypassing association you created :slightly_smiling_face: |
| # |
Feb 1st 2018, 11:04 |
neon1024 |
Self referencing aliased tables can be a bit fiddly imho |
| # |
Feb 1st 2018, 11:04 |
ooskar1233 |
has many old_clans, belongs to clan |
| # |
Feb 1st 2018, 11:03 |
ooskar1233 |
liek |
| # |
Feb 1st 2018, 11:03 |
neon1024 |
But I think you’d have to manage a bit of that process manually |
| # |
Feb 1st 2018, 11:03 |
ooskar1233 |
or just creating two associations |
| # |
Feb 1st 2018, 11:03 |
neon1024 |
@ooskar1233 Approach would also work, by creating a row in a clan history table |
| # |
Feb 1st 2018, 11:03 |
neon1024 |
You could set the condition on the association configuration |
| # |
Feb 1st 2018, 11:02 |
turkles |
Ah indeed |
| # |
Feb 1st 2018, 11:02 |
neon1024 |
So you don’t get a list of clan members who were in the clan as well as are currently |
| # |
Feb 1st 2018, 11:02 |
neon1024 |
Do remember to filter the association on the other end as well |
| # |
Feb 1st 2018, 11:02 |
neon1024 |
..and you’ll still be able to pull all the clans they’re “in” as “was in” |
| # |
Feb 1st 2018, 11:02 |
neon1024 |
Yep |
| # |
Feb 1st 2018, 11:01 |
turkles |
ok so I flag in the join table, and then I can use conditions on that flag if I only want the current |
| # |
Feb 1st 2018, 11:01 |
neon1024 |
@turkles Then you’ll have to use a `belongsToMany` with an `active` flag in the join table |
| # |
Feb 1st 2018, 11:01 |
ooskar1233 |
right, maybe you should just create other model for history? |
| # |
Feb 1st 2018, 11:01 |
turkles |
that ignores the history |
| # |
Feb 1st 2018, 11:01 |
neon1024 |
@ooskar1233 No, as then they could not join many clans |
| # |
Feb 1st 2018, 11:01 |
ooskar1233 |
even in English it's pretty resonable :) |
| # |
Feb 1st 2018, 11:01 |
ooskar1233 |
clan hasMany players, player belongsTo clan |
| # |
Feb 1st 2018, 11:00 |
neon1024 |
If you want to have a kind of ‘currently representing’ a certain clan, then that’s just a flag in the join table |
| # |
Feb 1st 2018, 11:00 |
neon1024 |
It’s either belongsToMany or hasOne, not both |
| # |
Feb 1st 2018, 11:00 |
neon1024 |
I don’t understand why one at a time is relevant |
| # |
Feb 1st 2018, 10:59 |
turkles |
Do I have to just name the 'current' clan association differently? |
| # |
Feb 1st 2018, 10:58 |
turkles |
How can I describe this relationship properly - A Player can join many clans, one after another, but only one at a time. I have Player belongsToMany Clans through PlayerClans. But I also have a clan_id in the player table which is the current clan. |
| # |
Feb 1st 2018, 10:40 |
ooskar1233 |
not too hard to migrate and get used to, though; I always been hacking bootstrap 3 to make the freaking flexboxes working |
| # |
Feb 1st 2018, 10:39 |
ooskar1233 |
basiaclly took flexbox on the 1st place |
| # |
Feb 1st 2018, 10:38 |
neon1024 |
Has v4 of Bootstrap changed a lot? I’ve not looked into it yet |
| # |
Feb 1st 2018, 09:58 |
birdy247 |
:slightly_smiling_face: |
| # |
Feb 1st 2018, 09:58 |
dereuromark |
birdy: did you try to look into the repo and look for open PRs? |
| # |
Feb 1st 2018, 09:58 |
birdy247 |
@neon1024 morning |
| # |
Feb 1st 2018, 09:58 |
birdy247 |
Hi, Are there any plans to make a bootstrap 4 FOC plugin branch? |
| # |
Feb 1st 2018, 09:49 |
neon1024 |
Morning all |
| # |
Feb 1st 2018, 09:07 |
ooskar1233 |
No problem, glad I could help. Cheers |
| # |
Feb 1st 2018, 09:06 |
dereuromark |
gsitex: use latest version of the IDE and it should be fine |
| # |
Feb 1st 2018, 09:05 |
hippo |
I'll have a go at it tomorrow again. Thanks for your help Oskar! <3 |