All my record on one indices was been deleted i don't know why. Is there a way to retreive them?
How can I cancel it?
The best way to debug that is to look at your Algolia logs, you can even inspect them at the index level.
It's unfortunately not cancelable (kind of similar to a database where you're not able to "cancel" DELETE options); you'll need to repush your data to Algolia.
Related
First I should say 'I'm new in the Odoo.'
I have a data which can't be deleted from database. In some framework like DevExpress, They achieve delete method by making inactive data.
So How do I achieve this result in Odoo?
I know little about unlink method. So What's the best practice in Odoo?
If it's possible please share some method.
You can also make records inactive in odoo those records will not be deleted but they will never effect anything in Odoo unless specifically searched for
Listening to documents changes on a Firestore Document is quite easy and works well.
I'm wondering though if there's any way to listen to a collection in a way we get notified when a document belonging to this collection is added/updated/deleted.
So far we can know everything that happens to a known document, but of course if it's a new document we definitely have no way to create in advance a listener on this document. Moreover, even if we were able to know in advance the new documents IDs, it's obvious that creating as many listeners as documents we have in a collection would be absolutely a bad practice.
My question in not specific to any language but for information I'm using flutter.
Does Firestore ecosystem provide a way to achieve this? Thanks in advance.
if it's a new document we definitely have no way to create in advance a listener on this document
That's not really true. You can construct a query that would yield a document before that document exists. A listener on that query will show the document as added in the event that it's created, and also satisfies the constraints of the query.
I don't know if flutter has very good documentation for this, but the core documentation for realtime updates shows how you can get snapshot changes when the results of a query change. Note that you can check the resulting query snapshot for documents that have been added, removed, or changed since the prior snapshot that was delivered to the listener.
The trick is to come up with a query that will tell you what you want to know. You will have to populate the document with enough information so that a listener can tell that it's a document of interest that was just created.
Is there a way to prevent deletion of objects in a mongoDB collection using a constraint or something else?
Maybe you are thinking: Why he doesn't prevent it in his code? Well I'm having an issue with a conflicting package (GroundDB) in my meteor/mongo app which delete records temporarily when syncing after and offline/online period. I need to dig into the issue but so far I want to workaround the issue. Actually it would be good to completely block deletion in that collection, since the user nor the administrator never requires to purgue that data (It's a kind of permanent log).
Thanks in advance.
I want to keep my list GWT side after fetch it from service side.For example i have button A and when i press, it bring me the list of patient names which start with 'A'. So; I don't want to fetch names from service side all the time. I want to take them for once and store in the cilent side. What am I suppose to do about it? Do you have any suggestion? Thanks.
Fetch them all at once at the beginning, and save them on a list and keep a reference of that list across the aplication (where you need it). Then every time you want to see more, just use that list and show the ones you wish to view. But keep in mind that if you have a lot of information on the server side, it might very well be better fetch just a few at the time, otherwise it might take a lot of time to get the bulk list at once.
At beginning fetch all list name and stored them. From this it will not provide u latest or frequented name list. so u can use gwt event service in gwt. I don't know the requirement but u can track like if new patient is added then it will fire the event from server to client and try to add that user also in that list.
Refer link:
http://code.google.com/p/gwteventservice/
I'm using Cloudant and I'm struggling to pull/replicate 600 documents from server to my iPhone. First, it's pretty slow because it has to go one-document-at-a-time, and Second Cloudant was giving me "timeouts" after the 100th-or-so REST request. (I have a ticket with Cloudant for this one, as it's unacceptable!)
I was wondering if anyone has found a way / hack to "bulk" replicate when pulling. I was thinking, perhaps it's possible to "zip up" all of the changes, send them in one file, and fast-forward the iPhone database to the last-change seq.
Any helps is great -- thanks!
Can you not hit _all_docs?include_docs=true to get everything in one shot? http://wiki.apache.org/couchdb/HTTP_Document_API#all_docs
I don't know couchcoccoa but it looks like the API supports this: http://couchbaselabs.github.com/CouchCocoa/docs/interfaceCouchDatabase.html#a49d0904f438587b988860891e8049885
Actually, why not make a view. Make a view that gives you your list and make sure your id is there. With your id, you can then go to the document and get all the rest of the required information that you need in order to update it if you need to.
There really is no reason you would ever need to hit every document individually. They have views and search2.0 for that. Keep in mind you are using a cloud based technology. This stuff is not sitting in your basement, you can't just hit it a million times per device in a few seconds and expect anyone to not notice and/or get upset (an exaggeration, yes I know).
What I do not understand is that you are trying to replicate it to an iPhone? Are you running apache and couchdb in your app? Why not just read the JSON data and throw it into a database. or just throw it into a file if it updates that much and keep overwriting it. There is so many options that are a whole lot less messy.