[sqlalchemy] Re: mapper for ms sql server

I'd be curious to see if it's really a lack of ALTER SCHEMA that's the culprit. Are you sure that the only thing you are varying to make it work is ALTER SCHEMA? This looks like a lack of access to the 'Sources' table, which can happen if the user that creates the table is missing certain properti

[sqlalchemy] MSSQL pyodbc - unicode problems since 0.5rc2

I'm using MSSQL + pyodbc + unixODBC + FreeTDS ... I have been tracking the 0.5 line for a while now, but I only recently noticed that I am unable to insert unicode into the database since 0.5rc2. Starting with 0.5rc3, when I do try to insert unicode into a column defined as Unicode or UnicodeText

[sqlalchemy] Re: MSSQL pyodbc connection string - broken for me!

On Dec 10, 3:05 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > this is just my 2c, im not here to say how it should be done or not. > I would think that the standard SQLA host/port connect pattern should > work as well if we just are aware of what kind of client library we're > talking to. If

[sqlalchemy] Re: MSSQL pyodbc connection string - broken for me!

On Dec 10, 1:27 pm, "Rick Morrison" <[EMAIL PROTECTED]> wrote: > This has been bandied back and forth for months, and I think it's becoming > clear that having sqla map dburl's to ODBC connection strings is a losing > battle. Yet another connection argument is not sounding very attractive to > me.

[sqlalchemy] MSSQL pyodbc connection string - broken for me!

mssql through pyodbc (and unixODBC and FreeTDS on debian) connections are broken for me when I pass a url to create engine. I can see that databases/mssql.py:make_connect_string has been changed to express host and port as ''server=," from "server=;port=" when the driver attribute is 'SQL Server'.

[sqlalchemy] Re: MSSQL null column definitions

There's now a ticket that addresses this, along with a patch: http://www.sqlalchemy.org/trac/ticket/1243 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalc

[sqlalchemy] MSSQL null column definitions

On MSSQL the default nullableness of a column, when neither NULL or NOT NULL are specified in the column definition, is configurable. The MSSQL dialect produces ANSI standard SQL when creating tables. So when a Column is specified with nullable=True, the DDL emitted contains neither NULL or NOT NU

[sqlalchemy] Re: mssql unicode weirdness: empty nvarchar string is selected as u" "

Almost forgot: I'm working against SQL Server 2000. --~--~-~--~~~---~--~~ 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 this group,

[sqlalchemy] mssql unicode weirdness: empty nvarchar string is selected as u" "

I'm setting up my first project that will use SA exclusively for database access and I've run into some behavior that seems odd to me. If I insert u"" into a column that is defined as nvarchar then when I select that column, I receive u" ". So I'm receiving a unicode string containing one space w

[sqlalchemy] Re: Accessing tables in multiple databases with one connection (MSSQL)

Hi Rick, On Jun 5, 4:05 pm, "Rick Morrison" <[EMAIL PROTECTED]> wrote: > I don't think so, not directly. I was afraid of this. > Short-term, here's a couple of things to try: [snip suggestions] I appreciate the suggestions. I may see about adding a view for this purpose. We decided against it

[sqlalchemy] Accessing tables in multiple databases with one connection (MSSQL)

Hi Folks, In my current environment, I get one database connection per web application. That connection has to access tables in a data warehouse as well as an application specific database. Both databases live on the same SQL Server instance. It seems as though I can't use the sql generation com

[sqlalchemy] Re: Null Foreign key issues

Hi wfpearson, On Apr 18, 1:21 pm, wfpearson <[EMAIL PROTECTED]> wrote: [snip full description of the problem] > I've tried the following method: > surgery = session.query(Surgery).select_by(dictation=None)[0] I'm pretty new to all of this myself, but maybe try using clause elements in yout sel

[sqlalchemy] Re: simple DateTime select

Hi Ryan, On Apr 7, 8:44 pm, "rkennedy" <[EMAIL PROTECTED]> wrote: > Thanks, Matthew. > > Looks like SA is still complaining about the global name not being > defined. > > > event = self.sess.query(model.Event).get_by(event_table.c.start_time < > > '2007-10-19 10:23:54') > > The above code produce

[sqlalchemy] Re: simple DateTime select

Hi Ryan, On Apr 7, 6:10 pm, "rkennedy" <[EMAIL PROTECTED]> wrote: > I'm new to SQLAlchemy and am trying to select objects from the > following table that occurred before a specified date. I'm pretty new myself, but I've been reading the docs a bunch today and I may be able to help. > event_tabl