I am having issue while trying to create an entity data model from postgresql database.
The issue is while trying to add the host name, the wizard disappears on typing the first letter itself.
Someone please help on this issue; really stuck at this issue
Related
I've an existing web app that is running in production with user data and various other types of data. I want to add a new model with some initial data for the same.
The data should be there when it goes live. This new data is a one time thing and I don't ever want it to be put back into the database in the future.
I couldn't find an answer to this specific scenario that I have. What is the best way to do this?
Thanks!
Hi fellow iOS developers, I have seem to run into a roadblock here with coredata and Im fairly certain this is should be a common use case. But I am either not querying google correctly or my design with handling managed objects was bad which led to this problem.
So basically, the problem that I am facing is the following..
User creates a new managed object object.
User updates said new managed object object (say edit the name
field)
** The following is the problem **
User wants to edit the same field again, but decides to discard their changes
What is the right thing to do here? Initially I was using .refresh() on the managed object context, but that only works if the object is persisted in the database.
Essentially, I don't want to save the object until the user explicitly opts to "save". Which leaves me in this limbo land. At first one of my thoughts was to created regular objects and convert them into core data objects when "save" is selected. However, that proved to be inefficient especially when handling multiple relationships.
I would think that there is something that is provided that aims to solve this problem, im just not quite querying google correctly.
so the fight with this tutorial goes on.
I made my own database(techbase.sql) and inserted two people into it - one of them with name of marian, adress menda and phone 112.
This application should log out in text fields: name, adress and phone from database when I input persons name into name field.
Saving properties into new database created "dynamically" in app works. But reading from db at start of the app doesn't.
What may be the problem? Have i specified name of db wrong? Or maybe the database table is made wrong?
Here is my project http://speedy.sh/D6hau/techtopiatut-3.zip if you would like to look in.
Thanks you in advance!
Just in case if this is confusing I will write easier:
-techbase.sql has two people in it
-cant log out their phone and adress by putting in name when I start app(like cant read db or something)
-can save and then log out but I want to read from pre-maid db. Not from table made in app.
Select your .sql database on the Xcode files list and then, in the right side, check that the Target Memership is correct (your target should be checked).
I have created a graph database from a pile of 30k xml files. I want to reuse this graph database for querying it. Currently, I create the graph database every time I have to query something from it. Since the data set is huge, the database creation takes approx. 40 min. I am not aware of the way of reusing the existing database instead of creating it every time. I would appreciate your help if you could tell me how to do this.
(Java language, IDE-> IntelliJ, Redhat Linux).
I am new in this, but I saw there is a Delete database method in several code. Perhaps this is your case. Try commenting out the delete database method o delete ir, and only use start and shutdown.
I am trying to know how use a database without start and shutdown each time Java code run, perhaps with api REST. I have no answer yet, but I am still searching.
First you should make sure your import logic and your query logic are not on the same code, and you can call on without the other.
The database you create is stored in a directory.
If you're on server mode, it is specified on the config file : neo4j-server.properties (look for org.neo4j.server.database.location).
If you're on embedded mode, you declare the path of the database to the graph factory:
graphDb = new GraphDatabaseFactory().newEmbeddedDatabase( PATH/TO/NEO.DB );
What do you mean by reusing? If you want to use the database from more than one client at the same time, use Neo4j Server and REST, see http://docs.neo4j.org/chunked/snapshot/rest-api.html and point the server to your database directory in conf/neo4j-server.properties.
Also, you can point a new instance of Neo4j to the same database directory and that way open the database you created (exclusively), see https://github.com/neo4j/neo4j/blob/master/community/embedded-examples/src/main/java/org/neo4j/examples/EmbeddedNeo4j.java#L35
Is that covering your usecase?
/peter
I just had the same problem, which resulted from sloppy copy pasting of the code snippets from the Neo4j documentation. Each time I ran the code, all previously created nodes were deleted.
Apart from deleting the removeData-method (as mentioned by Jose) you should also remove the following line in the createDb()-method to prevent this:
FileUtils.deleteRecursively( new File( DB_PATH ) );
Maybe this still helps anyone, even though the topic is old.
I am looking for a simple way to get data displayed in an issue as just plain text. Basically, I want to be able to type in a lookup id in the issue creation and then once the issue is created, it would call one of our web services to retrieve data connected with that ID.
This wouldn't be coming from another issue tracker, but rather straight from one of my databases.
What would be the easiest way of accomplishing this? I would like the workflow to be: Enter id #, hit save, see the data with that ID displayed in the ticket (Doesn't need to be editable, just displayed in the ticket view).
The easiest way is to create a workflow function that is triggered at Create transition to do the job. There your code can query information from the database and replicate them into JIRA standard and custom fields of the issue itself.
Then you can prevent edition of replicated fields by tuning Edit screen for your issues.
You can also use your function to update field content from time to time, either at transition or in a trigger.
An option is to create some read-only custom fields than query each piece information from the database. It will prevent data replication but it will be probably slow and it does not apply to default fields.