quattro_4 scribble

scribble 落書き (調べた事をただ落書きする)

thoughtbot Build Phase #37

Assume You're Sharding

Core Data Stack

database sharding

CoreDataをキャッシュに使う
sqlite fileを分けて、キャッシュのクリアをやりやすくする(ファイル削除するだけ)
tweetbot


wrapping up project
knowledge transfer
concrete implementation
data stucks
singleton
storyboard
didnt get any pain point
all of the views
merge conflict
tony merge
adding view controllers
same place
no conflict
coredata
threading issue
passing context model
chaining
application controller
beginning point
cascade down
coredata stuck
downside
bummer
smell
pass context
passing context down
passing objects down
single model
singleton objects
context run
view model should care data
data representation
why view model need to know
where model came from
oo design
boilerplate
managed object context
default context
never happy with that
sanely leeky
ns fetched result controller
validations
outside of coredata
setup stuck
fundamental
dealing with
threadsafe
activerecord
one context
entire app
mostly just work
find findall
no concurrency
sequel query
ironically enough
coredata has obvious
giving away from that
building table
schema drive ui
ui dectate schema
rails app
multiple users
coredata
much slower
read unread
twitter app
dont change very often
occasional deletion
need to be updated
cache tweet
tweetbot
brief conversation
database sharding
year ago
database shards with coredata
keep tweet
delete them all
one massive database
multiple sqlite file
delete files
different shards
different account
data gone
persistent store
not orm
dealt with
rake task
hidden api
prepackage
format
z underscore
change format
coredata
compatibility
no warning
objc command line client
object mapping