db_eng = sa.create_engine(url, **db_opts)
metadata.bind = db_eng
setup_all(True, checkfirst=True)
class TestMSSQLNumeric(unittest.TestCase):
def test_1(self):
obj = MSTSTA(
CMSTIDCD = 'UNG',
CMSTIDNM = 'Ungaran',
CMSTIDDS =
On Jan 2, 2009, at 7:51 PM, Eoghan Murray wrote:
>
> But the inner UNION doesn't work (postgres at least), as it seems to
> compute the union based on column position, rather than column label.
this is correct, unions work based on column position.
>
> At the moment I'm replacing the outer SEL
On Jan 2, 10:41 pm, Michael Bayer wrote:
>
> It would help if you could illustrate with accurate code - the UNION
> above does not have consistent numbers of columns in each select() and
> I think what you're trying to do is reverse f_1 and f_2 in the second
> select() statement which is al
Hi John,
On Fri, Jan 2, 2009 at 12:30 AM, Jaimy Azle wrote:
>
> using mssql with sqlalchemy 0.5rc4 for update process on a table that
> has Numeric field type will get an exception:
>
> 01-02-2009 11:59:15 [ INFO] File "D:\Enterprise Core
> Framework\script\ecf\core\sqlalchemy\databases\mssql.
On Dec 22, 2008, at 11:06 AM, Eoghan Murray wrote:
>
> The following example uses an elixir class:
>
> class MyE(Entity):
>id = Field(Integer, primary_key=True)
>f_1 = ManyToOne('OtherE')
>f_2 = ManyToOne('OtherE')
>date = Field(Date)
>
> MyE.query.select_from(union(MyE.table.sel
On Dec 22 2008, 7:10 pm, Eoghan Murray
wrote:
> On Dec 22, 4:16 pm, "Gaetan de Menten" wrote:
>
>
>
> > I'm not sure what you are trying to do, but MyE.f_1 and MyE.f_2 are
> > not column objects. f_1_id and f_2_id are.
>
> Sorry, I edited down my example from a bigger version and made a
> mistak
On Jan 2, 2009, at 1:08 PM, Andreas Jung wrote:
> On 02.01.2009 18:11 Uhr, Michael Bayer wrote:
>>
>> On Jan 2, 2009, at 4:24 AM, Andreas Jung wrote:
>>
>>> Hi there,
>>>
>>> running SA 0.5rc4, psycopg2 together with Postgres 7.4.22.
>>>
>>> I am currently migrating a Zope application from SA 0.
On 02.01.2009 18:11 Uhr, Michael Bayer wrote:
>
> On Jan 2, 2009, at 4:24 AM, Andreas Jung wrote:
>
>> Hi there,
>>
>> running SA 0.5rc4, psycopg2 together with Postgres 7.4.22.
>>
>> I am currently migrating a Zope application from SA 0.3 to SA 0.5.
>> While the migration worked for a bigger appli
I solved the problem dropping the tables as sysdba. :-)
j
jo ha scritto:
> Seems SA checks if table already exist in all_tables system table...
> and creates it only if it doesn't exist.
>
> In my case...
>
> SQL> select table_name from all_tables where
> table_name='FUNZIONE_CALCOLO', returns
On Jan 2, 2009, at 11:51 AM, jo wrote:
>
> Seems SA checks if table already exist in all_tables system table...
> and creates it only if it doesn't exist.
>
> In my case...
>
> SQL> select table_name from all_tables where
> table_name='FUNZIONE_CALCOLO', returns:
> TABLE_NAME
> -
if you are calling Table(, autoload=True), then you are executing
the query below as well as a result of that activity.
On Jan 2, 2009, at 7:22 AM, Ash wrote:
>
> but i dont want to see all this queries only the query i execute
>
> On Jan 1, 10:29 pm, Michael Bayer wrote:
>> thats the SQ
On Jan 2, 2009, at 4:24 AM, Andreas Jung wrote:
> Hi there,
>
> running SA 0.5rc4, psycopg2 together with Postgres 7.4.22.
>
> I am currently migrating a Zope application from SA 0.3 to SA 0.5.
> While the migration worked for a bigger application I have an issue
> with a smaller application. SA
session has an is_active flag which indicates this, but if you are
using autocommit=False, the Session is always within a transaction and
you should never call begin().
On Jan 1, 2009, at 11:52 PM, Jaimy Azle wrote:
>
> Hi All,
>
> I configure a session (from elixir) using this code:
>
> s
Seems SA checks if table already exist in all_tables system table...
and creates it only if it doesn't exist.
In my case...
SQL> select table_name from all_tables where
table_name='FUNZIONE_CALCOLO', returns:
TABLE_NAME
--
FUNZIONE_CALCOLO
SQL> select table_name fro
hi all,
I'm having problems with database.metadata.create_all.
The code works perfectly with PostgreSQL but with Oracle it
doesn't...and it exits with the following error:
...
self._execute_raw(context)
File "/usr/lib/python2.4/site-packages/sqlalchemy/engine/base.py",
line 581, in _exec
but i dont want to see all this queries only the query i execute
On Jan 1, 10:29 pm, Michael Bayer wrote:
> thats the SQL which SQLAlchemy is emitting.
>
> On Jan 1, 2009, at 2:31 AM, Ash wrote:
>
>
>
> > Hello
>
> > i am using sqlalchemy
>
> > and to trace the query i use metadata.bind.echo = T
Hi there,
running SA 0.5rc4, psycopg2 together with Postgres 7.4.22.
I am currently migrating a Zope application from SA 0.3 to SA 0.5.
While the migration worked for a bigger application I have an issue
with a smaller application. SA issues a "SAVEPOINT XXX" command although
Postgres 7.4 obviou
17 matches
Mail list logo