>[EMAIL PROTECTED] wrote:
> dananrg> Are you saying I'm getting the "L" as an artifact of printing?
>
> No, you're getting the "L" because you're printing a long integer. If you
> execute
>
> x = 872L
> y = 872
>
> at a Python prompt, x will be a long integer and y will be an integer. Lon
[EMAIL PROTECTED] wrote:
> # Print new list
> print recordList
>
>
[872L, 'ACTIVE', , >>>00EA1428>, None, '1.0.0.0', None, None, None]
Read the Python library manual chapter 2. Read all of it, it's all
very useful information, but take a particular look at str() and
repr(). All Python object
dananrg> Are you saying I'm getting the "L" as an artifact of printing?
No, you're getting the "L" because you're printing a long integer. If you
execute
x = 872L
y = 872
at a Python prompt, x will be a long integer and y will be an integer. Long
integers can represent arbitrarily
> If you actually get a suffixed L in the resulting text file, you
> are using a strange way to convert your data to text. You aren't
> simply printing lists or tuples are you? Then other types, such as
> datetime objects will also look bizarre. (Not that the ancient
> odbc would support that...)
>
[EMAIL PROTECTED] wrote:
> The other thing I didn't do a good job of explaining is that I want to
> have a layer of abstraction between the underlying RDBMS and the
> business logic. It's the business logic I want to use Python for, so
> that would stay roughly the same between RDBMS changes, if we
[EMAIL PROTECTED] wrote:
> This is from a database I didn't design and can't change. The problem
> is that the ODBC module suffixes an "L" to any integer returned that
> was defined as data type number(p). For example, an integer stored as:
> 56 will be returned as 56L. Numbers that were specifie
The other thing I didn't do a good job of explaining is that I want to
have a layer of abstraction between the underlying RDBMS and the
business logic. It's the business logic I want to use Python for, so
that would stay roughly the same between RDBMS changes, if we ever have
an RDBMS change. I agr
Thanks Gerhard and Magnus. Magnus, thanks for the references. I will
follow up on those.
I was messing around with the native ODBC module you mentioned (I am
using Python in a Win32 environment), e.g:
import dbi, odbc
...and it seems to meet my needs. The only issue I've had so far is
retrieving
Jonathan Gardner wrote:
> On database portability...
>
> While it is noble to try to have a generic interface to these
> libraries, the end result is that the databases are always different
> enough that the interface just has to work differently.
Considering the use case in question...
"What I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> What would be the next best Oracle database module for Python next to
> cx_oracle?
That would probably be DCOracle2.
> I'd like to compare two and choose one, just for the sake of
> seeing how two modules doing the same th
Also, what's the difference between something like cx_oracle and an
ODBC module? If I were to use an ODBC module (not trying to torture
myself here, I promise, but I just want to see what alternatives exist
and how they work).
--
http://mail.python.org/mailman/listinfo/python-list
What would be the next best Oracle database module for Python next to
cx_oracle? I'd like to compare two and choose one, just for the sake of
seeing how two modules doing the same thing operate.
Also, does installing cx_oracle create registry entries or require
admin privs on a Windows XP machine?
I've never seen the points of those tools. Just lay it out on paper or
document it somewhere. Be consistant with your naming scheme and it
shouldn't be hard to see the relations. If found that the people who
don't understand how tables should relate to one another are also the
same people who don't
How about DBdesigner4 or Dia as free ER diagrammers?
[EMAIL PROTECTED] wrote:
> Thanks Olivier and Jonathan.
>
> Do either of you, or anyone else, know of a good open source data
> modeling / ER-diagram / CASE tools? I'd like to be able to build
> relatively simple schemas in one open source too
Thanks Olivier and Jonathan.
Do either of you, or anyone else, know of a good open source data
modeling / ER-diagram / CASE tools? I'd like to be able to build
relatively simple schemas in one open source tool and be able to create
a database on different platforms as needed (e.g. MySQL, PostgreSQ
On database portability...
While it is noble to try to have a generic interface to these
libraries, the end result is that the databases are always different
enough that the interface just has to work differently. My experience
in going from one database to another is that you should revisit your
[EMAIL PROTECTED] a écrit :
> I'm a little confused about what's out there for database modules at:
>
> http://python.org/topics/database/modules.html
>
> What I'd like to do is use Python to access an Oracle 9.X database for
> exporting a series of tables into one aggregated table as a text fi
I'm a little confused about what's out there for database modules at:
http://python.org/topics/database/modules.html
What I'd like to do is use Python to access an Oracle 9.X database for
exporting a series of tables into one aggregated table as a text file,
for import into a mainframe database
18 matches
Mail list logo
