Reply to thread

Message: <blockquote data-quote="RastaLulz" data-source="post: 368145" data-attributes="member: 1"><p>I assume your issue is that that you're accessing a value that has already been gathered (via a select query) and stored to a variable before you've gone ahead and ran a query to update the ticket? Obviously the value isn't going to to automagically change in that case. It's hard to specifically solve your issue without seeing how the ticket is being accessed on the client, and whether the solution would be to simply access that value and set it to the new one (when you fire the update query), or to have a method in a class called getTicket(), which would access the newly generated ticket in both the update and on the client, as opposed to querying the old ticket that was probably initialized early in the app's boot.</p></blockquote><p></p>