The earlier version of dgraph-orm provided logging of the queries by default but after the latest update it has been turned off. So is there any way to turn on the logging. I need to debug and find out if the queries being fired are correct.
This is what I have tried:
dgraph.connect(config.database.dgraph);
dgraph.logging((a)=>console.log(a));
The version that I am using is 1.2.2.
I have checked any its working fine, find the snippet below
import dgraph from 'dgraph-orm';
// you can pass your logger function here
dgraph.logging(console.log);
I'm using Orchard 1.7
In Orchard, when a content item is removed, it don't actually deleted from database, the cms just only set Published & Latest value of all versions of content item to 0, it still can be retrieved
And my problem is: I have a user that was removed (this user was modified many times, especially the Title)
Case 1: I use cms.Get(userId, VersionOptions.AllVersions).As<TitlePart>()
Case 2: I use myItem.As<CommonPart>().Owner.As<TitlePart>()
And the result is it always returns the title of the first version of this user, I want it return the latest version (the largest version number) of it.
So, where in Orchard should I modify to resolve this ?
I had this issue too. Here is my solution to query the recent version of a deleted user by using the content manager:
Orchard.Users.Models.UserPart lUserPart = mContentManager
.Query<Orchard.Users.Models.UserPart,
Orchard.Users.Models.UserPartRecord>(VersionOptions.AllVersions)
.Where(u => u.NormalizedUserName == lowerName) // taken from Orchard.Users.Services.MembershipService.GetUser()
.List()
.LastOrDefault(); // LastOrDefault() to get version with highest version number
I have my app setup with v2.0.6 right now and I can create Date Tabs.
In v2.1+ I cannot.
Now Signer.Tabs.DateTabs.Add(item as Date?) is asking for System.DateTime.Date? instead of DocuSign.eSign.Model.Date
And Signer.Tabs.DateTabs = New List(Of [Date]) no longer works, it wants Signer.Tabs.DateTabs = New List(Of Date?) which will not work.
Anyone know a fix or workaround? Right now I have to stay on v2.0.6
This looks like a bug with the DocuSign.eSign.dll nuget package v2.1.4
I have logged the following issue
https://github.com/docusign/docusign-csharp-client/issues/135
Update
This bug has been fixed with DocuSign.eSign.dll v2.1.7
I made a mass edit to a bunch of docs in my couchdb, but I made a mistake and overwrote a field improperly. I can see that the previous revision is there. How do I revert back to it?
My current best guess, based on this:
http://guide.couchdb.org/draft/conflicts.html
...is to find the doc id and the revision id and then send a delete for that document specifying the revision I want to be gone.
curl -X DELETE $HOST/databasename/doc-id?rev=2-de0ea16f8621cbac506d23a0fbbde08a
I think that will leave the previous revision. Any better ideas out there?
I had to write some coffeescript (using underscore.js and jquery.couch) to do this. It's not a true revert, as we are getting the old revision and creating a new revision with it. Still looking for better suggestions:
_.each docsToRevert, (docToRevert) ->
$.couch.db("databaseName").openDoc docToRevert.id,
revs_info: true
,
success: (doc) ->
$.couch.db("databaseName").openDoc docToRevert.id,
rev: doc._revs_info[1].rev #1 gives us the previous revision
,
success: (previousDoc) ->
newDoc = previousDoc
newDoc._rev = doc._rev
result.save newDoc
I had a core data EntityDescription and I created data in it. Then, I changed the EntityDescription, added new one, deleted the old one using the editor for xcdatamodeld file.
Now any of my code for core data causes this error "The model used to open the store is incompatible with the one used to create the store}". The detail is below. What should I do? I prefer to remove everything in the data model and restart new one.
Thanks for any suggestion!
reason=The model used to open the store is incompatible with the one used to create the store}, {
metadata = {
NSPersistenceFrameworkVersion = 320;
NSStoreModelVersionHashes = {
Promotion = <472663da d6da8cb6 ed22de03 eca7d7f4 9f692d88 a0f273b7 8db38989 0d34ba35>;
};
NSStoreModelVersionHashesVersion = 3;
NSStoreModelVersionIdentifiers = (
);
NSStoreType = SQLite;
NSStoreUUID = "9D6F4C7E-53E2-476A-9829-5024691CED03";
"_NSAutoVacuumLevel" = 2;
};
Or if you're in dev mode, you can also just delete the app and run it again.
Deleting the app is sometimes not the case! Suggest, your app has already been published! You can't just add new entity to the data base and go ahead - you need to perform migration!
For those who doesn't want to dig into documentation and is searching for a quick fix:
Open your .xcdatamodeld file
click on Editor
select Add model version...
Add a new version of your model (the new group of datamodels added)
select the main file, open file inspector (right-hand panel) and under Versioned core data model select your new version of data model for current data model
THAT'S NOT ALL ) You should perform so called "light migration".
Go to your AppDelegate and find where the persistentStoreCoordinator is being created
Find this line if (![_persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:nil error:&error])
Replace nil options with #{NSMigratePersistentStoresAutomaticallyOption:#YES, NSInferMappingModelAutomaticallyOption:#YES} (actually provided in the commented code in that method)
Here you go, have fun!
P.S. This only applies for lightweight migration. For your migration to qualify as a lightweight migration, your changes must be confined to this narrow band:
Add or remove a property (attribute or relationship).
Make a nonoptional property optional.
Make an optional attribute nonoptional, as long as you provide a default value.
Add or remove an entity.
Rename a property.
Rename an entity.
Answer borrowed from Stas
If this is a non-production app, just delete your local database (appname.sqlite) and restart the app.
I find I'm always doing this, and so provide the following additional detail:
Under XCode 4 (4.3.2) you should find your datastore here:
/Users/~/Library/Application Support/iPhone Simulator/simulatorVersion/Applications/yourAppIdentifier/Documents
Or you can use Spotlight, if you first enable searching for System Files; I've found it fastest to save such a search to the menu bar.
If this is a non-production app, just delete your local database (appname.sqlite) and restart the app.
Delete your app on simulator and restart:
On simulator, go to Hardware -> Home:
Click and hold mouse button on your application icon:
Click on "X" in app icon to delete:
Go back to Xcode and restart your application(Command+R):
or:
PS.:
If the error appears again, review your code because the problem should be in the syntax or discrepancy between what you want to list with the data model that you have.
Reset your simulator and run again. If you were to run with a different device in the simulator, it would work. If you are running with an iphone 6s simulator and you try to run 6s plus, it would still work without resetting.
If running on a phone, make sure to delete the app and rerun it
I have faced the same issue using Xcode 7 beta 1 and the following action has resolved the issue.
Menu==>> click on Window>Projects>select project on the left hand side and click on delete button which is located on the right side.
If still doesn't work,
=> reset the simulator and run the app