Nope. Use the latest git trunk of pg8000, 1.07 has bugs. Note it was
released on Jan 9 2009.
I actually tried really hard to do that, really I did. :) Github was broken or
something last night -- it wouldn't zip the files.
BTW, let me make sure my install procedures are correct:
1. Go to
Nope. Use the latest git trunk of pg8000, 1.07 has bugs. Note it was
released on Jan 9 2009.
I actually tried really hard to do that, really I did. :) Github was broken
or something last night -- it wouldn't zip the files.
BTW, let me make sure my install procedures are correct:
1.
So, I'm using PG8000 1.07 and SqlAlchemy 0.6beta1dev_r6718 and I get this error:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x8d in position 3: ordinal
not in range(128)
I saw a past message about this same thing that said to use a newer version of
PG8000
Well, as far as I can tell,
The method that works 95% of the time is, just establish a connection to the
database, start a transaction, do some work that stays within the thread,
commit the transaction. Then throw all loaded state in that thread away, and
reload it all on the next transaction.
Its only if you
it really is that - simultaneous transactions are isolated from one another,
and their results are only made visible to other transactions after they're
committed. as far as locking, you generally choose between an optimistic
and a pessimistic approach:
Thanks.
Ok, so I found an article
Basic question:
I have 1 app with multiple processes and threads. Each thread
and/or process may end up trying to do something to the database at the
same time. What is the solution to threading? How do web frameworks
solve it? Is there some inherent design in databases and/or SQLAlchemy
