Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>you just need to access the data stored within the appdelegate. I dont think this is the best solution to your problem but in order to do things the way you want.</p> <p>so declare you property in your Appdelegate .h file </p> <pre><code>NSMutableArray* myArray_; </code></pre> <p>then add a property to the same file </p> <pre><code>@property (nonatomic, retain) NSMutableArray* myArray; </code></pre> <p>in the .m file </p> <p>make sure you synthesize your property </p> <pre><code>@synthesize myArray = myArray_; </code></pre> <p>somewhere in your appdelegate .m file you will set the value</p> <p>then, elsewhere in your code you can access the property in the appdelegate like so </p> <pre><code>MyAppDelegate *appDelegate = (MyAppDelegate *)[UIApplication sharedApplication].delegate NSMutableArray* localArray = appDelegate.myArray; </code></pre> <p>Note, for good encapsulation you should really use an NSArray but i used mutable to keep the code short. </p> <p>Also, using the appdelegate as a global store for program data is not a good idea, it breaks a lot of rules you shouldnt break, single responsibility principle being a good one to start with. You should ideally be storing application data in a dedicated class, perhaps a singleton or for much better testability a single instance class served by a factory class. This way you data is accessible from a known well defined entity, it is testable and it honours good design principles</p>
    singulars
    1. This table or related slice is empty.
    1. POPassing Objects Between Classes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMatt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIn my case, would you just recommend a singleton class? Basically I have a list of 10 channels. For each channel I need to store three things: now, next and later. So something like two embedded NSDictionaries in a singleton class would do it? Please note I am also talking about good design. Good design is as important as functionality to me.
      singulars
      1. PO
      1. USdarksky
    2. COSingletons are controversial see this article http://www.ibm.com/developerworks/webservices/library/co-single/index.html they do have their place but they break a lot of good practices such as the single responsibility principle, is so much as they are responsible for the functionality they provide to your app as well as managing the fact that there is only one instance, they also make testing hard. There are some more elaborate ways of better engineering things using a factory to manage singleton-ness. A whole book could be dedicated to this subject, id recommend reading about it..
      singulars
      1. PO
      1. USMatt
    3. COpersonally it sounds like the only thing that differentiates now, next and later is the time at which you look at that data, although this makes assumptions on how you request the data and how it is returned. Why not model a channel as an object it is responsible for knowing its programmes and then have some operations for determining which is now, next or later, you may need a channelManager class which contains the channels objects you will also probably find that it helps to model a request as an object and build some code around that for making requests and processing responses. up to you
      singulars
      1. PO
      1. USMatt
 

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