Hi Rick,
I still have rowcount issues on the latest svn. Also, is 'money' a
native type? I'm currently setting
ischema_names['money'] = MSNumeric
Thanks,
Graham
On Jun 6, 6:34 pm, Rick Morrison [EMAIL PROTECTED] wrote:
Hi Graham,
There's a good chance that only you and I are using
I'm bringing this old thread up because I'm still having the same
issue with 0.3.8. In order to use mssql I have to add
def max_identifier_length(self):
return 30
to the pymssql dialect.
I also find that I need to set has_sane_rowcount=False (as I have had
to with every
Hi Graham,
There's a good chance that only you and I are using pymssql, and I don't
have have the long identifiers problem, so it kind of dropped throught the
cracks, sorry.
I've checked in the 30-character thing, but I've left off the sane_rowcount
for now. I had run into issues with that back
Hello,
Michael Bayer said the following on 08.05.2007 20:57:
overheard at firebird developer meeting:
hey, whats the longest table names should be ?
obviously, 31 characters.
hey yeah. 31 does it for me. brilliant !
Just for reference. Here is (slightly outdated) information on
To add a little more info, 0.3.6 generates:
SELECT [T_Event].[EventLastCancellationDate] AS
[T_Event_EventLastCancell_8ab9]
whereas 0.3.7 generates
[T_Event].[EventLastCancellationDate] AS
[T_Event_EventLastCancellationDate]
From what I can find, column names can be up to 128 chars in SQL
SA is now doing no column truncation for MS-SQL, as we have not
placed any limit within the MS-SQL dialects. previously, SA was
truncating all identifiers to 30 characters for all dialects
(including those that had much larger limitations), and it would
search for these truncated names
On May 1, 2007, at 7:50 AM, Graham Stratton wrote:
To add a little more info, 0.3.6 generates:
SELECT [T_Event].[EventLastCancellationDate] AS
[T_Event_EventLastCancell_8ab9]
whereas 0.3.7 generates
[T_Event].[EventLastCancellationDate] AS
[T_Event_EventLastCancellationDate]
From
s/DBAPI/DBlib/
On 5/1/07, Rick Morrison [EMAIL PROTECTED] wrote:
The label-truncation code is fine. The issue isn't SA. It's the DBAPI that
pymssql rides on top of...identifier limit is 30
chars, is deprecated by Microsoft, it will never be fixed.
Try pyodbc, which has no such limitation.
On May 1, 2007, at 11:18 AM, Rick Morrison wrote:
The label-truncation code is fine. The issue isn't SA. It's the
DBAPI that pymssql rides on top of...identifier limit is 30 chars,
is deprecated by Microsoft, it will never be fixed.
Try pyodbc, which has no such limitation.
OK well,
The underlying DBlib limits *all* identifier names, including column names
to 30 chars anyway, so no issue there.
Where does the character limit go in the dialect? Can I follow Oracle as an
example?
On 5/1/07, Michael Bayer [EMAIL PROTECTED] wrote:
On May 1, 2007, at 11:18 AM, Rick
10 matches
Mail list logo
