On Mon, Sep 26, 2011 at 11:05 PM, Michael Bayer wrote:
> On Sep 26, 2011, at 2:50 AM, Nathan Robertson wrote:
>
>> Column('custid', Integer, Sequence('test.customer_custid_seq'),
>> primary_key=True),
>
> for the Sequence, as with all schema items, you need to specify the "schema"
> portion
On Mon, Sep 26, 2011 at 11:05 PM, Michael Bayer
wrote:
> On Sep 26, 2011, at 2:50 AM, Nathan Robertson wrote:
>
>> Column('custid', Integer, Sequence('test.customer_custid_seq'),
>> primary_key=True),
>
> for the Sequence, as with all schema items, you need to specify the "schema"
> portion
On Sep 26, 2011, at 9:13 AM, Kent wrote:
> Oh, yes, I had already imagined these types of scenarios, so I
> appreciate how the change from () to [None] could break several other
> things (which is why I didn't touch it).
> We'll certainly move to 0.7, just under much pressure currently to get
> f
Oh, yes, I had already imagined these types of scenarios, so I
appreciate how the change from () to [None] could break several other
things (which is why I didn't touch it).
We'll certainly move to 0.7, just under much pressure currently to get
functionality in place and I already know 0.7 breaks s
On Sep 26, 2011, at 2:50 AM, Nathan Robertson wrote:
> Column('custid', Integer, Sequence('test.customer_custid_seq'),
> primary_key=True),
for the Sequence, as with all schema items, you need to specify the "schema"
portion separately so that SQLAlchemy knows where each token starts and
func.sum(), being a known generic function in sql/functions.py, by default
will denote the return value as having the same SQL type as the value that was
passed in. The BigInteger type object though doesn't do any python-side
processing right now, its assumed DBAPIs can handle sending an int.
Hello,
Rpclib aims to save the protocol implementers the hassle of implementing
their own remote procedure call api and the application programmers the
hassle of jumping through hoops just to expose their services using
multiple protocols and transports.
It currently supports XmlSchema and SOAP
Hi,
I've come across a bug (hopefully in my configuration) where
SQLAlchemy will generate an INSERT statement for a table with a SERIAL
primary key which PostgreSQL errors on. I'm running EnterpriseDB's
Postgres Plus 8.4 on openSUSE 11.4 x64, with Python 2.7, SQLAlchemy
0.7.2 and psycopg2 2.4.2. F
Hello.
Why func.sum(some_table.c.bigintfield) returns Decimal ?
documents_table.c.sum has BigInteger type (postgresql table field has
bigint type)
the same issue I got with postgresql date_part func, when I extract
year or month I got Decimal result, not int
>>> s = select([func.sum(document
