Hi list -
Alembic 0.6.4 is released.
This release has a bunch of fixes that have been piling up; in particular, a
whole bunch of fixes to work with the new naming_convention feature in
SQLAlchemy 0.9, and ever more fixes regarding autogenerate with indexes and
unique constraints.
As
On Fri, Mar 28, 2014 at 1:16 AM, thatsanicehatyouh...@mac.com wrote:
Hi,
I'm trying to configure a table with autoload but can't quite get the syntax
to set up a self-relationship. This is my abbreviated) schema:
CREATE TABLE sdssphoto.photoobj
(
pk bigint NOT NULL DEFAULT
On Fri, Mar 28, 2014 at 5:42 AM, Eric Kiser erickise...@gmail.com wrote:
CURRENT SCENARIO:
- we have been given access to a network hence we can share copy and paste
files on it. We access it by ftp://xx.x.x.xx with a user and password.
THE IDEA ON MIND:
- Create a simple program that uses
On Mar 28, 2014, at 1:15 AM, Adrian Robert adrian.b.rob...@gmail.com wrote:
I have been using the automap extension with postgres, with an inheritance
structure using the joined inheritance pattern. I could not figure out a way
to have this reflected from the DB so I define the classes for
If you can only use FTP, then your options is probably just to write a
program that downloads the sqlite via ftp, does the queries, then uploads.
that's going to be messy with race conditions though, so you'd have to
create some sort of system where the file is renamed/hidden, downloaded,
I couldn’t tell you, it shouldn’t happen in the first place. Would need code
that illustrates the problem.
On Mar 27, 2014, at 9:27 PM, Ni Wesley nisp...@gmail.com wrote:
MySQLdb has the same problem.
So, no concurrent, I just use engine(with default connection pool) execute.
Then, how to
On Mar 28, 2014, at 6:40 AM, Simon King si...@simonking.org.uk wrote:
The alternative is to define the children relationship after the
class has been defined:
class PhotoObj(Base):
__tablename__ = 'photoobj'
__table_args__ = {'autoload':True, 'schema':'sdssphoto'}
This problem seems to appear with SQLAlchemy 0.8 and above. A correction
works for me and has been accepted here :
https://github.com/monetizeio/sqlalchemy-orm-tree/pull/1
Le vendredi 25 janvier 2013 01:50:50 UTC+1, Pirate Fibonacci a écrit :
Mark,
I'm trying to test run your above example
Hi All,
I am trying to port my application from MySQL to Sybase ASE 15.7 version.
How can i implement my query using LIMIT and OFFSET using sqlalchemy 0.8
targeting Sybase ASE 15.7 ?
Thanks,
Angad Nath
--
You received this message because you are subscribed to the Google Groups
sqlalchemy
Hi list -
SQLAlchemy release 0.8.6 is now available.
Release 0.8.6 contains a variety of bugfixes backported from the 0.9 series.
Areas of fix include ORM issues as well as dialect-specific issues.
Users should carefully review the Changelog at
Hi list -
SQLAlchemy release 0.9.4 is now available.
0.9.4 contains mostly bug fixes, split across regressions local to 0.9 as well
as more general issues. There are also some new features, in particular a major
change to the testing system to support py.test in addition to nose.
Many
Hi list -
Alembic 0.6.4 is released.
This release has a bunch of fixes that have been piling up; in particular, a
whole bunch of fixes to work with the new naming_convention feature in
SQLAlchemy 0.9, and ever more fixes regarding autogenerate with indexes and
unique constraints.
As
The Sybase dialect supports rendering of the TOP and START AT clauses when
you use the limit() and offset() constructs of select().
So if you're using Core SQL select() constructs or the ORM Query, it should
work at least rudimentally.
On Mar 26, 2014, at 4:19 AM, angad nath
13 matches
Mail list logo
