Last week I was getting an error when trying to save an entity containing more than 20 synonyms. Does anyone know if this limit was removed and if so, what is the limit now?
Soon! It is a limitation in the simulator, we are actively working on a fix. Stay tuned.
Related
As of late, I have encountered a problem with my view index being rebuilt all the time and users are having massive issues with this particular view.
I figured it was due to #Date in my selection formula aswell as one of my column formulas. This way the selection formula would be different every second that passes.
So I figured, since I dont need hours/minutes/seconds in my formulas, I would use #Today. This worked out well for 2-3 days and after that the same problem occured again.
So since the problem is back again, I'm not quite sure if that even causes the problem. When this particular view is open, I have issues in every tab that's open in notes, not only this specific database.
Is this a common/known issue? What can I do to avoid this problem?
Yes, it's a common issue that has been well known since the very early days of Notes more than 20 years ago.
#Date is not a problem on its own. #Now and #Today are both problems.
Using #TextToTime("Today") was a popular workaround that was discovered early on. This hid the problem from the indexer so the server failed to realize that the view was out of date. It doesn't solve the underlying problem, though, which is that the view is trying to do something that views simply aren't designed to do. Views are intended to be static, requiring update only when documents change. Introducing time into a selection or column formula makes them dynamic, which kills that presumption and is a major source of performance problems. Using this workaround requires that the view be fully rebuilt every night. You can do that by setting the view index options to "Manual", and setting up a program document to run an updall command with the -T option for the specific database and view once per night. Note that if your users are spread out across timezones, you'll have to pick one specific time as your standard, and if you have servers spread out across timezones you're going to have a lot of fun figuring out how to make them all show the same documents in the view at all times - but that's common to pretty much all approaches to the problem.
See this IBM Technote for a description of several other options that people have used over the years, with their pros and cons. Also see this article by Andre Guirard, which covers date/time issues in great detail.
I would add that the agent-and-folder solution that they describe in the Technote was generally my preferred approach, but it does have an additional disadvantage that they don't mention: it can eventually lead to an obscure situation where the server throws an error "Folder is larger than supported". This error actually has nothing to do with the size of the folder in documents; it refers to fragmentation of internal structures that occurs as large numbers of documents are moved in and out of the folder over time. It could only be fixed by deleting and re-creating the folder, which you can do in your agent code. I believe this problem may be fixed in more recent versions of Domino, but it caused me a lot of grief back in the Notes 6 and 7 timeframes.
I have an iOS turn-based match app using GameKit. Recently, I've had some matches on Game Center disappear. It's about one in six with no rhyme or reason. GKTurnBasedMatch.loadMatchesWithCompletionHandler fetches Game Center matches successfully, but a few of my ongoing or old matches are no longer there. However, when I go to the separate Game Center app and look at my Turns, I can see the missing matches there -- my app just can't access them.
the weird thing is that it is only a fraction of the total that have disappeared. Not sure if it matters, but when this happened I had more than 30 total matches but fewer than 30 active matches. The issue occurs both in sandbox and production versions. Has anyone else seen this issue?
According to this wwdc session http://asciiwwdc.com/2013/sessions/506 a game can have up to 30 matches. The speaker doesn't describe what happens if you try to create a 31st. It appears, based on your experience, that any extras are subject to disappearing.
I have never seen this limit mentioned in any of the game center docs, just in the wwdc videos.
I have a MonoTouch.Dialog with UIViewElements that contain a UIWebView. This is a messaging type app and messages are constantly being added. I can ealisy get over 1000 UIViewElements and there is no limit. Obviously memory is going to be an issue.
What is the best way to only keep the last 100 rows?
I need a first in first out type setup. I can manually remove the Elements but do not know if there is a better way.
As far as I know, you do have to do this manually. I used TweetStation as an example.
Though this is not the latest app you can get (2010), it does cover a lot of the basics you need to understand.
Here is more information on building custom cells, if you do not know already.
The core part of managing your list of elements is to override the CreateSizingSource-method on your inheriting DialogViewController-class and creating your own SizingSource as shown in this part of TweetStation.
I hope this will get you started.
All 16 of these venues have same name and same lat/lon.
In this case, their category is private residence, so that helps make a decision as to what to do with them and it turns out to not be a problem, but still, what's going on? Is this something to worry about?
https://foursquare.com/v/puamana-condos/4ce1ef7b70bba1cd8e7574c4
https://foursquare.com/v/puamana-condos/4ce18e8e78ddf04db02cac98
https://foursquare.com/v/puamana-condos/4ce18eb7ffcf3704f4842682
https://foursquare.com/v/puamana-condos/4ce18ebec4f6a35dd2fddb6c
https://foursquare.com/v/puamana-condos/4ce18ec469136dcbb332eae6
https://foursquare.com/v/puamana-condos/4ce18ec678ddf04dd72dac98
https://foursquare.com/v/puamana-condos/4ce18ec77e2e236ac60e911b
https://foursquare.com/v/puamana-condos/4ce18ec8f8cdb1f717549d12
https://foursquare.com/v/puamana-condos/4ce18ec994c3b60c455577ea
https://foursquare.com/v/puamana-condos/4ce18eca825e721ec75c7c45
https://foursquare.com/v/puamana-condos/4ce18ecb3644a093f4c65d9f
https://foursquare.com/v/puamana-condos/4ce18ed9f8cdb1f75e549d12
https://foursquare.com/v/puamana-condos/4ce18ee4ffcf3704fe852682
https://foursquare.com/v/puamana-condos/4ce18ef3db125481d59242ce
https://foursquare.com/v/puamana-condos/4ce18ef9aba88cfa690556d7
https://foursquare.com/v/puamana-condos/4ce1ef4fc4f6a35d2f29de6c
It looks like all these venues were created by a single user on a single day back in December 2010. This was before we implemented more rigorous checking about existing duplicates before creating new venues, so it was probably a side effect of a poor connection / multiple creation attempts. Marking them as dupes and this should be cleaned up soon.
Because they're homes, they don't show up in normal "nearby" queries, which is why our SU community probably hadn't found them till now.
Can someone explain why this is happening? I'm using their TranslationContainer sample they've provided.
This strikes me as wrong; if I'm translating lots of small pieces of text I'm going to be changed per translation rather than against my quota of characters.
Can someone explain what's happening here
As of today, this is how the Translator service usage is measured. The default transaction length is 1,000 characters.
EDIT 3/18/2012: I reached out to the team and heard back: You are getting the proper number of characters per month, per subscription details, but the counter display isn't reliable at the moment. A fix is coming. I don't have an exact date for the fix.
EDIT 5/17/2012: Looks like this has been fixed. There's also a blog post about real-time updates to remaining characters per month, as well as low-balance notifications: