Thanks! Anyway I've seen that it's better add extensions in Elixir,
into a declarative layer, just as has been made in DataMapper.
http://elixir.ematia.de/apidocs/elixir.ext.html
On 7 dic, 14:54, Michael Bayer [EMAIL PROTECTED] wrote:
we have a bitbucket mirror
On Mon, Dec 8, 2008 at 10:31, Kless [EMAIL PROTECTED] wrote:
Thanks! Anyway I've seen that it's better add extensions in Elixir,
into a declarative layer, just as has been made in DataMapper.
As I just said on the Elixir mailing list: not really. The ability to
add new types is an SQLAlchemy
I cant find in the PG docs why it would raise this but the DISTINCT is
not needed here.
On Dec 8, 2008, at 6:05 AM, Ash wrote:
Hello ,
I am usinng sqlalchemy for making the sum on column i am using
sqlalchemy.func.sum (col_name).
I am getting the error while dng it .
Code snnipet
I'd like to be able to map read-only attributes based on a join, but
without mapping the class to a joined table.
Given this structure:
class unit:
pass
class recsite:
pass
units = Table('units',metadata,
Column('unit_id',Integer,
On Dec 8, 2008, at 2:18 PM, channing wrote:
I'd like to be able to map read-only attributes based on a join, but
without mapping the class to a joined table.
Given this structure:
class unit:
pass
class recsite:
pass
units = Table('units',metadata,
hi
back to that old question about relation vs query,
i have some relation, say m2m via table with some additional fields
like timestamps (which are setup automaticaly).
so plain relation via secondary join is ok, no really need for
explicit assoc_object.
by default, the relation will give
On Dec 8, 2008, at 3:49 PM, [EMAIL PROTECTED] wrote:
hi
back to that old question about relation vs query,
i have some relation, say m2m via table with some additional fields
like timestamps (which are setup automaticaly).
so plain relation via secondary join is ok, no really need for
On Monday 08 December 2008 23:39:57 Michael Bayer wrote:
On Dec 8, 2008, at 3:49 PM, [EMAIL PROTECTED] wrote:
hi
back to that old question about relation vs query,
i have some relation, say m2m via table with some additional
fields like timestamps (which are setup automaticaly).
so
On Monday 08 December 2008 23:39:57 Michael Bayer wrote:
On Dec 8, 2008, at 3:49 PM, [EMAIL PROTECTED] wrote:
hi
back to that old question about relation vs query,
i have some relation, say m2m via table with some additional
fields like timestamps (which are setup automaticaly).
so
How can I prevent aliases fro appearing in the query?
I have hit a MySQL bug that is related to a very biq SQL query string
being sent and I am trying to shorten it.
I might need an alias on one of the columns, though.
The query is created originally by ORM query.compile() and then I
create a
you'd need to be more specific what you mean by aliases (it sounds
like you mean labels) and what the actual issue is. If its label
names too long, use the latest 0.5 release candidate and set
label_length=0 to create_engine().
also if you are using select() constructs generated by Query,
11 matches
Mail list logo
