On Dec 21, 3:51 am, Keith Rarick <[email protected]> wrote: > Beanstalkd has no function for that. You could scan through all the > jobs yourself. If you need to do it a lot, you might consider building > an auxiliary data structure to make this faster. For example, in a > key-value store, you could map the hash of the job body to the job id. > Or you could use a full-text index of some sort. > > kr
Are Job IDs persistent too (in 1.43) I mean? Or do IDs get reset when beanstalk is restarted? -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
