Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I used RESTKit until the .20 release a few months ago. In all honesty, while this library has great intentions, in my experience it ends up wasting far more time than it was ever meant to save me. </p> <p>I have used it with API's created with .NET/MVC, PHP, python/Django/TastyPie, and hacked it to do some stuff with Twitter. This all ended up being a very interesting academic exercise, but in the end was little more than that. Both the old/new versions of RESTKit assume ALOT about the way your API is going to be responding to requests. </p> <p>With the .10 release, there was a fair amount of customizability through the use of Obj-C Blocks. I could intercept the request/response of an RKRequest and pretty much override anything that RESTKit was going to do. This seemed fairly awesome. Now with the .20 release, everything got very... <strong>clever</strong> (clever code is usually not good). </p> <p>Instead of trying to remain generic and malleable, RK now does all kinds of "convenient" things for you. This effectively takes away your ability to jam it into whatever (non-idealized and realistic) shape your API has taken. At this point, I have gone back to writing all of my code using <a href="https://github.com/AFNetworking/AFNetworking/" rel="noreferrer">AFNetworking</a>. I'd rather take the extra time to write my own parsing code, and know that when my Unit Tests pass, I'm done. NOT spend hours trying to get RK to log out meaningful error messages.</p> <p>The other real problem with RK was that it does not account for being offline. It was designed with the assumption that your application is ALWAYS online, and simply mirrors a persistant store in the sky. My applications all handle content-creation on an iOS device, which MAY OR MAY NOT be online at the time of content-creation. This is the main reason I was "customizing" RK .10. When I saw the changes in .20, I decided enough was enough, and went back to doing things the <em>old way</em>.</p> <p>Maybe I'll just write my own CRUD/RESTful framework, cause I'm starting to get tired of spending time using very specialized libraries, that try to do everything with as little responsibility being left to the application developer as possible. Frameworks like this tend to be Swiss Army Knives. They look really awesome on paper, <em>THEY CAN DO ANYTHING</em>, then you actually try to cut something and the blade is too dull or breaks off. Good software does very few things very well, and if it sounds too good to be true, it probably is.</p>
    singulars
    1. This table or related slice is empty.
    1. PORestKit and saving to CoreData as NSManagedObject
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USG. Shearer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORestKit and saving to CoreData as NSManagedObject
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI understand you point of view. This would deserve some debate. As an Objective-C beginner (coming from python world), I admit I haven't yet been able to do anything with RestKit. BUT trying to be the devil's advocate, we can skip whatever suggested RK's _smart layer_ we want and it seems to be designed also for offline content with his [CoreData integration](https://github.com/RestKit/RestKit/wiki/Object-mapping#core-data) isn't it ? I naïvely tend to think that these upvotes are coming more from people discouraged by the complexity than from people understanding the whole stack.
      singulars
      1. PO
      1. USPierre de LESPINAY
    2. COAs a python programmer, perhaps you are familiar with Django? Django is a pretty large framework, but it is EASY and very DRY. I love Django, so at least for me personally, the size of RESTKit has little to do with my issue. I have an issue with the overcomplicated design. I built my first Django App in about an hour (with a working ORM). I built my first RESTKit service (on a real API) in just over 4 hours. And RESTKit is really a toolkit for one kind of problem, while Django is a full application framework. I'm talking about the simplicity of good design.
      singulars
      1. PO
      1. USG. Shearer
    3. COAnd I should really say, my first production RESTKit service took about 4 hours to get ANYTHING working. I worked on getting 6 different endpoints working with no mapping issues for over 2 weeks. Thats too much, If I were smart I would have just written my own client like I have in all my other software before RK.
      singulars
      1. PO
      1. USG. Shearer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload