title: Is Core Data more suitable than SQLite for server client database design?
body: <p>I'm having a server client database design which I'm unsure is Core Data suitable?</p>
  
  <p>I have a server database which will maintain the master copy of the data and their relationship.</p>
  
  <p>Each client application will have an empty client database with only relationship.</p>
  
  <p>Upon the start up of the client, it will request for data from the server and try to populate it with data.</p>
  
  <p>As the relationship in the client database will cause the insertion to fail, the client will compile a list of information that it is still lacking and make the necessary request until it succeed in inserting all information.</p>
  
  <p>So in conclusion, client will have only a subset of data from the server.</p>
  
  <p>In my design, the primary keys and relationships have to be managed by the server database.</p>
  
  <p>But it seems that Core Data purposefully abstract the management of primary keys and relationships.</p>
  
  <p>I can either emulate my own primary keys and relationships mechanism using Core Data. While reaping the benefit of what Core Data provides.</p>
  
  <p>Or implements SQLite and handle my own data.</p>