I am unable to join two or three tables with the custom grid app. Is there any other way to acheive the same?
More details would clarify what problem you are trying to solve, but this post has an example of a custom app that builds a grid based on data from two different stores.
One store uses a Task object, the other uses UserIterationCapacity object. Since currently it is not possible to create a Rally.data.WsapiDataStore with more than one model, two WsapiDataStore objects are created in that example. Eventually a custom store Rally.data.custom.Store is created that accesses the fields pulled from the two models, and a grid is built based on the custom store.
Related
We are experimenting with using Graphileon to create a database of related terms. To do this, we are accessing a data store located on a server. We are able to see nodes and relationships that are added by other users, but the styling applied to these nodes is not carrying over.
Is there a way to make the styling universal for the entire data store and anyone accessing it? Or is any styling of nodes and relationships specific to the user who configured it?
In principle styling is specific to the user. Since you are having multiple users, you are probably not using the personal edition. Can you confirm this?
i want to generate Model and CRUD automatically when my new table created.
i am creating new table(xyz_uid) dynamically after successful registration of user. and i am inserting some data related to that particular user. this thing is working fine for me.
i creating separate table for each user because for every user table attributes may different and i tried to keep one table instead of making new table for every user but it's smashing everything in my project.
i want to generate Model and CRUD of that user so i can do future transaction with that table.
i know how to generate Gii manually from ?r=gii. but here i want to generate automatically from back end.
i tried to search about this in Yii forum and in google also. but i didn't found anything.
is there any extension or anything which will generate it automatically.
will it be good idea to create model and CRUD for every table? or shall i communicate with table directly using CDbCommand?
you may use giix-core.
While You install the giix-core it's create the model and basemodel so if u have any changes in DB every time u can create the basemodel not a model.
so it's easy working and u can use method override.
Note: Please make sure you can not write any code in BaseModel
for more please refer following link...
http://www.yiiframework.com/forum/index.php/topic/13154-giix-%E2%80%94-gii-extended/
I've been developing several iOS applications using Core Data and it has been an excellent framework to work with. However, I've encountered an issue whereby we more or less have distributed objects (synced) across multiple platforms. A web/database server backend and mobile devices.
Although it hasn't been a problem until now, the static nature of the data model used by Core Data has me a little stuck. Basically what is being requested is a dynamic forms system whereby forms can be created on a server and propagated to the devices. I'm aware of the technique for performing this with a set number of tables with something like:
Forms table
Fields table
Instance of Forms table
Instance Values table
and just linking everything together. What I'm wondering however is if there is an alternative system to Core Data (something above talking to an SQLite database directly) that will allow for a more dynamic object graph. Even a standard ORM would be good if there are options for modifying the schema at runtime. The main reason I want to go down this route is for performance in the sense that I don't want the instance values table exploding with entries (on the local device or server).
My other option is to have the static schema (object-graph) on the iOS devices but have a conversion layer on the server's side which fetches the correct object, populates the properties and saves it to the correct table. Then when the devices comes to sync, it does the reverse and breaks it down into instances. While this saves the server from having a bloated instance value table, it could still be a problem on the device.
Any suggestions are appreciated.
Using specific tables/entities for forms and fields, and entities for instances of each, is probably what I would recommend. Trying to manipulate the ORM schema on the fly if it's going to be happening frequently doesn't seem like a good idea in general.
However, if the schema is only going to change infrequently, you can probably do it with Core Data. You can programatically create and/or manipulate the NSManagedObjectModel prior to creating a NSManagedObjectContext. You can also create migration logic so data stored in an old model can be preserved when you update the model and need to recreate the context and stores.
These other SO posts may be helpful:
Customize core data model at runtime?
Handling Core Data Model Changes
You need to think carefully about what you are actually modeling.
Are you modeling: (1) the actual "forms" i.e. UI elements, (2) data that might be presented in any number of UI versions e.g. firstName or (3) both?
A data model designed to model forms would have entities like:
Form{
name:string
fields<-->Field.form
}
Field{
width:number
height:number
xPos:number
yPos:number
label:sting
nextTab<-->Field.priorTab
priorTab<-->Field.nextTab
form<<-->Form.fields
}
You would use this to store data about form as displayed in the user interface. Then you would have a separate entities and probably a separate model to store the actual data that would populate the UI elements that are configured by the first data model.
You can use Core Data to modeling anything you just need to know what you are really modeling.
I'm pretty new to Core Data, and I'm trying to wrap my head around it.
You might have cases where you want different types of data stored in different places or with different behaviors. For example you might have one read only sqlite store shipped as part of your app containing some default data, an additional store for updates to that data set you have downloaded from a server, and a third for user data. Alternately you might have a case where you want some objects to be persisted while others can live in an in-memory store and do not need to be saved between uses of the app.
i'm trying to create a RDCL report with the follow requirements:
The datasource is a master business object that also has a child business object.
I want to show some data of the master BO using a List.
I want to show the details of the child BO using a Table.
I do not want to use subreports.
I do not want to flatten my object graph and use grouping
Is this possible?
I am not sure you can achieve what you're looking for. Either you must use subreports or by definition of master-child data you must use grouping.
I know this answer comes on late but this post still shows on search results and it has 1K views.
Hope this helps!