FAQ update: DBIC and fork/threads #65
Conversation
dbsrgits-sync
force-pushed
the
current/for_cpan_index
branch
from
e81ec1f
to
e52712a
Compare
|
Sorry for the delay in updating this - looking into the way we currently handle things, combined with a recent bugreport are making me rethink a lot of how we are currently handling things, which may in turn invalidate parts of the proposed text. Will get you another update in couple days. Thanks for the patience! |
|
The bug I referenced above still hasn't been fixed - the rabbit hole goes deeper and deeper. I just wanted to update you that I have this PR on my radar and it will definitely be acted upon before next stable. Cheers! |
dbsrgits-sync
force-pushed
the
current/for_cpan_index
branch
from
4aaf6fd
to
b3f3814
Compare
dbsrgits-sync
force-pushed
the
current/for_cpan_index
branch
2 times, most recently
from
11cec86
to
2a89732
Compare
dbsrgits-sync
force-pushed
the
current/for_cpan_index
branch
from
1282683
to
4bfba4e
Compare
dbsrgits-sync
force-pushed
the
current/for_cpan_index
branch
from
0824a0c
to
ca30d84
Compare
|
@davewood Apologies for the closure of this issue - github did a number on me due to how it operates wrt disappearing branches. The issue is still on the radar, and will be merged when the underlying piece falls in place (any moment now). Sorry about that. |
thanks ribasushi
http://lists.scsys.co.uk/pipermail/dbix-class/2006-June/001690.html
http://stackoverflow.com/a/14701914/1702521