On Dec 3, 2007, at 6:33 PM, imgrey wrote:
>
>> I think the error throw of the IntegrityError is totally expensive
>> from both a DB perspective as well as a python perspective. if
>> missing data is truly so rare then it might be fine, but the
>> necessesity of then using SAVEPOINT seems to com
>I think the error throw of the IntegrityError is totally expensive
>from both a DB perspective as well as a python perspective. if
>missing data is truly so rare then it might be fine, but the
>necessesity of then using SAVEPOINT seems to complicate things more
>than necessary. but you'd have t
On Dec 3, 2007, at 4:59 PM, Mike Orr wrote:
>> oh...well actually in this case its because MSDateTime doesn't do any
>> date/time conversion, since mysqldb returns datetime objects for us
>> and we dont need to convert from strings...we only do it for sqlite
>> right now. if MySQL itself is ret
On Dec 3, 2007 1:33 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
> On Dec 3, 2007, at 4:05 PM, Mike Orr wrote:
>
> >
> > On Nov 30, 2007 9:28 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
> >>
> >> yes...add type_=DateTime to your coalesce() call -
> >> func.coalesce(date1, date2, type_=DateTim
A composite type would be perfect for me.
> Michael Bayer wrote:
> > you cant do it right now. but its something we could support. its
> > unclear to me if we should just go for "composite types" as the way to
> > do it, or just use a callable. using a composite is likely cleaner
> > a
thanks, i've updated the docs
On Dec 3, 2007 9:35 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 3, 2007, at 4:32 PM, Brendan Arnold wrote:
>
> >
> > hi there,
> >
> > i'm trying to delete an object from my database using the orm.
> > according to 'sqlalchemy for people in a hurry do
On Dec 3, 2007, at 4:32 PM, Brendan Arnold wrote:
>
> hi there,
>
> i'm trying to delete an object from my database using the orm.
> according to 'sqlalchemy for people in a hurry docs 0.4' there is a
> delete() method on orm objects, so the following is possible,
>
> sample.comments[0].delete()
On Dec 3, 2007, at 4:05 PM, Mike Orr wrote:
>
> On Nov 30, 2007 9:28 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
>>
>> yes...add type_=DateTime to your coalesce() call -
>> func.coalesce(date1, date2, type_=DateTime)
>
> This doesn't work, I'm afraid.
oh...well actually in this case its becaus
hi there,
i'm trying to delete an object from my database using the orm.
according to 'sqlalchemy for people in a hurry docs 0.4' there is a
delete() method on orm objects, so the following is possible,
sample.comments[0].delete()
del sample.comment[0]
and this will delete the comment from the
id look at prop = MyClass.someattribute.property, use isinstance(prop,
PropertyLoader) to determine a relation and not a scalar, combined
with getattr(prop, "direction") == sqlalchemy.orm.sync.MANYTOMANY,
ONETOMANY, etc. to get the type of join.
On Dec 3, 2007, at 3:43 PM, Brendan Arnold wr
This is on MySQL 5.0.45, BTW.
--
Mike Orr <[EMAIL PROTECTED]>
--~--~-~--~~~---~--~~
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
On Nov 30, 2007 9:28 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> yes...add type_=DateTime to your coalesce() call -
> func.coalesce(date1, date2, type_=DateTime)
This doesn't work, I'm afraid.
# Table t_incident defined with
sa.Column("orr_id", sa.types.Integer, primary_key=True),
s
hi there,
i'd like a way to determine if an attribute of an orm object is:
a:) a sqlalchemy generated list of objects (i.e. many-to-many)
b:) a single sqlalchemy joined object (i.e.one-to-many)
c:) a 'scalar' loaded from the database (i.e. a string, float, integer)
at present i'm co
is that something looking like real concrete-polymorphism?
AFAIremember there was something composite there in the pattern.. the id is
actualy (id,type)
Michael Bayer wrote:
> you cant do it right now. but its something we could support. its
> unclear to me if we should just go for "composi
you cant do it right now. but its something we could support. its
unclear to me if we should just go for "composite types" as the way to
do it, or just use a callable. using a composite is likely cleaner
and would integrate with the "save" process better (otherwise, the
callable needs
I'd like to make a polymorphic mapper based on two columns. Is that
possible?
See example code here: http://paste.pocoo.org/show/13799/
Thanks, Koen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group
On Dec 3, 3:26 pm, voltron <[EMAIL PROTECTED]> wrote:
> import Guard, as in the tutorial does not work. Any ideas?
I am not familiar with Python on Windows, but does your installation
directory appear in your sys.path?
-Samuel
--~--~-~--~~~---~--~~
You received t
Hi!
import Guard, as in the tutorial does not work. Any ideas?
Easy:installing was problematic, but installing( and python setup.py
install) from the download worked.
I' m using windows python 2.4
Thanks!
On Dec 2, 11:07 pm, Samuel <[EMAIL PROTECTED]> wrote:
> Introduction
>
> S
18 matches
Mail list logo
