On Fri, 14 Sep 2012 16:36:58 +1000, Chris Angelico wrote:
> Actually I haven't used Postgres with Python yet. Should probably do
> that at some point. But the MySQL bindings for Python aren't so awesome
> they can't be matched by any other.
I have found psycopg2 excellent in every respect.
--
ht
On Fri, Sep 14, 2012 at 4:28 PM, Ben Finney wrote:
> Chris Angelico writes:
>
>> Don't use MySQL. :) Okay, that's hardly a *rule*, but it's a strong
>> recommendation.
>
> That's another struggle we have in our future, unfortunately.
We moved from MySQL to PostgreSQL a little while ago, and have
Emile van Sebille writes:
> The only standard I'm aware of is the EDI specification which I first
> encountered in the mid 70's and which is updated routinely. The full
> spec is the size of a telephone book (do they even still make those?)
Thanks, that's something to look into. And yes, in Melb
On 9/13/2012 8:02 AM Ben Finney said...
Howdy all,
What material should a team of programmers read before designing a
database model and export format for sending commerce transactions to a
business accounting system?
The only standard I'm aware of is the EDI specification which I first
encou
On Fri, Sep 14, 2012 at 1:02 AM, Ben Finney wrote:
> What I want is pointers to a putative “What every programmer needs to
> know about storing commercial transactions for business accounting”
> general guide.
>
> Does that information already exist where I can point our team to it?
Not a guide p
Howdy all,
What material should a team of programmers read before designing a
database model and export format for sending commerce transactions to a
business accounting system?
I'm especially not wanting ad hoc advice in this thread; this is surely
an old, complex problem with a lot of ground al
