Can anyone answer these specific questions or point me in the
direction of some further documentation?
I assume that the SA doc, chapter object relational tutorial does
best clearify how to create and use a session.
http://www.sqlalchemy.org/docs/04/ormtutorial.html
Or are there some
Simon,
Simon Pamies wrote:
Hi,
although I said I would start on Friday if there are no objections, I
couldn't longer resist to revamp autocode and so I moved it to google
code.
Please have a look at http://code.google.com/p/sqlautocode/ for the
changes and the current structure.
I also
On Oct 11, 8:05 am, Nebur [EMAIL PROTECTED] wrote:
Can anyone answer these specific questions or point me in the
direction of some further documentation?
I assume that the SA doc, chapter object relational tutorial does
best clearify how to create and use a
Michael,
Michael Bayer wrote:
On Oct 10, 2007, at 5:56 AM, Werner F. Bruhin wrote:
Looking at the doc for 0.4 I see that I should be able to do this:
result = engine.execute(select username from users)
... do something with the result
result.close()
But I am getting the following
On Oct 10, 2:12 pm, Marco Mariani [EMAIL PROTECTED] wrote:
James Brady ha scritto:
The problem I'm hitting at the moment is how to properly select simple
objects... There seems to be two main approaches, for example:
session.query(Ownership).select() or
James Brady ha scritto:
Hi Marco, assign_mapper did help - the relations are now accessible
through my models, and the query syntax is nicer than pure SA as well
in my opinion.
However, I'm using the identity framework (part of TurboGears)
Me too.
which unfortunately doesn't play nicely
On 10/11/07, James Brady [EMAIL PROTECTED] wrote:
Did you call assign_mapper on Ownership?
[...]
However, I'm using the identity framework (part of TurboGears) which
unfortunately doesn't play nicely with assign_mapper... shame!
If you use SA 0.3.10 I would advise you to use mapper
Hi,
It's really good to see this script progressing.
BTW, with SA 0.4, this script should be able to work with no
database-specific hacks at all. If you're interesting in implementing this,
I can explain more.
Paul
--~--~-~--~~~---~--~~
You received this message
Trying to fix the NumericTest (testtypes.py) for firebird backend, I
came to this patch for FBNumeric:
+def bind_processor(self, dialect):
+return None
+
+def result_processor(self, dialect):
+if self.asdecimal:
+return None
+else:
+def
On Oct 11, 2007, at 5:25 AM, Werner F. Bruhin wrote:
Could you give me some hints on how I could do the following in SA.
- define a column as I18N (actual value is a varchar)
- when the column is read take the value from the table column, do a
lookup with it in the i18n translation table
Michael,
Michael Bayer wrote:
First of all, thanks for this response.
i'd embed the SP call explicitly in the select():
select([table.c.id, table.c.foo, table.c.bar, func.convert_I18n
(table.c.data).label('data')]).where(...)
if using the ORM, set up the column explicitly:
Hello again,
I'm running into a new set of errors when I attempt to save objects to
the database, then interrogate their properites. Here is an example
of my latest problem:
I have a very simple class called Compound which stores a creation
date, a smiles string (string representation of a
At Thu, 11 Oct 2007 18:28:10 +0200,
Werner F Bruhin wrote:
My first go at this did not work, it might have to do with
FB/kinterbasdb as it expects the stored procedures to be called in one
of these ways.
cur.execute(select output1, output2 from the_proc(?, ?), (input1, input2))
I performed a release under LGPL. Hope that this is ok and fits into
the sqlalchemy environment.
Why not just release it under MIT like SQLAlchemy? The project will
likely receive wider use under MIT rather than LGPL.
--~--~-~--~~~---~--~~
You received this
SEE INDIAN SEXY VIEDO AND PICS
http://chromoo.blogspot.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from
15 matches
Mail list logo