Hi,
unfortunately my time-limited trial license of the easysoft driver
already expired so i cannot check it further.
thanks anyway for your wilingness to help.
regards,
stefan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
If Migrate is no longer actively maintained then it should be removed
the the SA front page and FAQ (plus other documentation) as it is
quite misleading to direct someone to a moribund project.
--~--~-~--~~~---~--~~
You received this message because you are
On Jul 4, 5:20 am, Noah Slater [EMAIL PROTECTED] wrote:
If Migrate is no longer actively maintained then it should be removed
the the SA front page and FAQ (plus other documentation) as it is
quite misleading to direct someone to a moribund project.
or, someone could spend a week or two
I still think the documentation should be updated - be it help rescue
the Migrate project or whatever. It is misleading not to mention it's
(current) moribund nature.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
So if I change it to say The Migrate project, which is currently
seeking developers, intends to provide schema migration support as
well., would that have prevented whatever frustration you've
experienced ? (since i am sensing frustration).
Yes, a certain level of frustration is bound to
On Jul 4, 2007, at 11:51 AM, Noah Slater wrote:
I still think the documentation should be updated - be it help rescue
the Migrate project or whatever. It is misleading not to mention it's
(current) moribund nature.
OK, i just went to the homepage to re-read whatever big shiny thing I
On Jul 4, 5:22 pm, Paul Johnston [EMAIL PROTECTED] wrote:
Hi,
select and select_by are exactly the methods that wont be directly off
the class; they will be available as class.query.select_by(whatever).
Personally, I would like the most common methods to stay - probably
select, select_by
On Jul 4, 2007, at 6:19 PM, Jose Galvez wrote:
Dear Micheal,
so far I really like all the new stuff, especially using the query
generator. I've got a question, what is going to be the preferred
method to replace get (or get_by). What I've been using is
On Jul 4, 7:30 pm, Jose Galvez [EMAIL PROTECTED] wrote:
Thanks Michael,
I went back and reread the Proposal thread and I finally get what
scalar() does and how it is different form one(). but how would first()
differ from scalar() and how would all() differ from list()? At first
blush
Hello,
I wanted an in-depth understanding of what goes on in connection
management in sqlalchemy. I want to use sqlalchemy for it's
connection management but I'm planning on building my own custom orm.
I just can't deal with assign_mapper and the stuff that goes on
underneath the covers. I've
On Jul 4, 10:22 pm, SamDonaldson [EMAIL PROTECTED] wrote:
I want to use MetaData() to return an object passed in it is the db
uri. I want the connection object returned back to me from the meta.
meta = MetaData(db_uri)
#getting the connection object
conn = meta.connect -- is this
the new interface is super clean, consistent and flexible. and
with that, we are able to add more features onto it. a cluttered
interface doesn't accept new functionalities as easily.
There was one more difference betwen filter* and select* - first is
just building a query, 2nd is building
12 matches
Mail list logo
