The only reason I want the hash is that I don't want a copy of this
string laying around. I also don't need to know what it is, I just need
to know if it's different. Think of this as a tripwire - if someone's
user access level is changed, we find out.
I still think using a separate database (s
On 12/2/2010 5:06 PM, draeath wrote:
On Thu, 02 Dec 2010 22:55:53 +, Tim Harig wrote:
Thanks for taking the time to check in on this, Tim!
I realize this could likely all be done from inside the database itself -
but altering the DB itself is not an option (as the product vendor is
very t
On Fri, 03 Dec 2010 02:19:54 +, Tim Harig wrote:
> a whole bunch of useful stuff
Certainly some good points for me to chew on... thanks!
--
http://mail.python.org/mailman/listinfo/python-list
On 2010-12-03, MRAB wrote:
> On 03/12/2010 01:42, Tim Harig wrote:
>> On 2010-12-03, draeath wrote:
>>> On Thu, 02 Dec 2010 22:55:53 +, Tim Harig wrote:
>>>
>>> Thanks for taking the time to check in on this, Tim!
>>>
So, basically, you want to store a local copy of the data and sync it
On 03/12/2010 01:42, Tim Harig wrote:
On 2010-12-03, draeath wrote:
On Thu, 02 Dec 2010 22:55:53 +, Tim Harig wrote:
Thanks for taking the time to check in on this, Tim!
So, basically, you want to store a local copy of the data and sync it to
the original.
In a way. I only need to store
On 2010-12-03, draeath wrote:
> On Thu, 02 Dec 2010 22:55:53 +, Tim Harig wrote:
>
> Thanks for taking the time to check in on this, Tim!
>
>> So, basically, you want to store a local copy of the data and sync it to
>> the original.
> In a way. I only need to store one copy of the data, and ma
On Thu, 02 Dec 2010 22:55:53 +, Tim Harig wrote:
Thanks for taking the time to check in on this, Tim!
> So, basically, you want to store a local copy of the data and sync it to
> the original.
In a way. I only need to store one copy of the data, and make note of
changes between it and the cu
On 2010-12-02, draeath wrote:
> The idea is that this script will run periodically, pulling the table,
> and comparing the data gathered at that run to that stored by the
> previous, acting on changes made, and storing the current data back (to
> be referenced against in the next invocation)
S
I'm going to be writing a utility that will be pulling three fields from
a MySQL table. I've already got a sample dataset - there's a long int
(which is a db key), a short string, and a looong string. Many rows.
As it is, receive this data from the DB interface as a rather large tuple
of tuples