thank a lot Oleg.
have a nice day.
On Fri, Dec 20, 2024 at 4:56 PM Oleg Broytman via Python-list <
python-list@python.org> wrote:
> Hello!
>
> I'm pleased to announce version 3.12.0, the release of branch
> 3.12 of SQLObject.
>
>
> What's new in SQLObject
> ===
>
> Drivers
> -
#I'm pleased to announce version 3.4.0, the first stable release of branch
#3.4 of SQLObject.
#
#
#What's new in SQLObject
#===
#
#* Python 2.6 is no longer supported. The minimal supported version is
# Python 2.7.
Is there a particular reason to eliminate RHEL 6 (Python 2.6)
Thanks for the info
On Mon, May 8, 2017 at 1:25 AM, Oleg Broytman wrote:
> Hello!
>
> I'm pleased to announce version 3.3.0, the first stable release of branch
> 3.3 of SQLObject.
>
>
> What's new in SQLObject
> ===
>
> Features
>
>
> * Support for Python 2.6 is decl
Thanks a million Oleg!
Cheers,
Daniel
On 11/20/11, Oleg Broytman wrote:
> Hello!
>
> I'm pleased to announce version 1.2.0, the first stable release of branch
> 1.2 of SQLObject.
>
>
> What is SQLObject
> =
>
> SQLObject is an object-relational mapper. Your database tables are
On Sep 28, 9:41 pm, Daniel Fetchinson
wrote:
> > I'm new to using SQLObject, and having some problems with getting it
> > to recognise my current MySQL database.
>
> > I've set up my connection fine, but it won't recognise the names of
> > the columns (presumably because they're not written using
> I'm new to using SQLObject, and having some problems with getting it
> to recognise my current MySQL database.
>
> I've set up my connection fine, but it won't recognise the names of
> the columns (presumably because they're not written using the default
> naming convention?). For example, one o
Hi,
Oleg Broytmann wrote:
> I'm pleased to announce version 0.11.1, a minor bugfix release of 0.11 branch
> of SQLObject.
Have you considered making announcements about (minor) releases on the
dedicated Python announce list?
Stefan
--
http://mail.python.org/mailman/listinfo/python-list
> I don't want to start a flame war and would just like some information
> before diving in--
> What are some the advantages and disadvantages of SQLObject compared to
> SQLAlchemy?
In short: sqlobject is much simpler (to use, to understand, etc) than
sqlalchemy and so I prefer it in small project
I don't want to start a flame war and would just like some information before
diving in--
What are some the advantages and disadvantages of SQLObject compared to
SQLAlchemy?
Thanks,
William
From: Oleg Broytmann
To: Python Mailing List ; Python Announce Mailin
Excellent stuff Oleg, I've been looking for an ORM framework for a while and
hadn't settled on one, I'll give this a look through later today.
Thanks,
Robert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Oleg Broytmann
Sent: 11 March 2008 13:40
To: Pyt
On Jan 10, 6:38 am, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I'm pleased to announce the 0.9.3 release of SQLObject.
>
> What is SQLObject
> =
>
> SQLObject is an object-relational mapper. Your database tables are described
> as classes, and rows are instances of thos
Hi,
you should ask SQLObject related questions better at
"SQLObject discussion" <[EMAIL PROTECTED]>
Oleg Broytman and others are very helpful there.
Markus
--
http://mail.python.org/mailman/listinfo/python-list
bruce wrote:
> hi...
>
> this continues my investigation of python/sqlobject, as it relates to the
> need to have an id, which is auto-generated.
>
> per various sites/docs on sqlobject, it appears that you can override the
> id, by doing something similar to the following:
>
> def foo(SQLObject
On Dec 28, 11:27 pm, "bruce" <[EMAIL PROTECTED]> wrote:
> i'm playing around, researching sqlobject, and i notice that it appears to
> require the use of "id" in each tbl it handles in the database.
> is there a way to overide this function/behavior...
there better be such way. An ORM that does
bruce schrieb:
> hi
>
> i'm playing around, researching sqlobject, and i notice that it appears to
> require the use of "id" in each tbl it handles in the database.
>
> if i already have a db schema, and it doesn't use 'id' as an auto-generated
> field, does that mean that i can't use/impleme
On Dec 29, 12:27 pm, "bruce" <[EMAIL PROTECTED]> wrote:
> hi
>
> i'm playing around, researching sqlobject, and i notice that it appears to
> require the use of "id" in each tbl it handles in the database.
>
> if i already have a db schema, and it doesn't use 'id' as an auto-generated
> field,
On Saturday 20 Oct 2007 5:43:48 am Sean DiZazzo wrote:
> Hi all,
>
> I am just beginning with TurboGears and have run into a problem with
> SQLObject.
>
> I'm trying to connect to an established mysql DB, and use TurboGears
> to display results from the DB only. The problem is that the DB
> alread
On Oct 19, 11:51 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Sean DiZazzo schrieb:
>
> > Hi all,
>
> > I am just beginning with TurboGears and have run into a problem with
> > SQLObject.
>
> > I'm trying to connect to an established mysql DB, and use TurboGears
> > to display results from t
Sean DiZazzo schrieb:
> Hi all,
>
> I am just beginning with TurboGears and have run into a problem with
> SQLObject.
>
> I'm trying to connect to an established mysql DB, and use TurboGears
> to display results from the DB only. The problem is that the DB
> already has an 'id' field that is a s
- Original Message -
From: "Oleg Broytmann" <[EMAIL PROTECTED]>
To: "Python Announce Mailing List" <[EMAIL PROTECTED]>;
"Python Mailing List"
Sent: Thursday, July 26, 2007 7:23 AM
Subject: SQLObject 0.7.8
> Hello!
>
> I'm pleased to announce the 0.7.8 release of SQLObject.
>
> What is
Hello!
On Fri, Jul 27, 2007 at 08:21:00AM -0700, george williams wrote:
> - Original Message -
And what is the question?
Oleg.
--
Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
--
http:
Steve Holden <[EMAIL PROTECTED]> writes:
> Sherm Pendley wrote:
>> Steve Holden <[EMAIL PROTECTED]> writes:
>>
>>> Sherm Pendley wrote:
Gerardo Herzig <[EMAIL PROTECTED]> writes:
> So..at 11:23 we got version 0.7.8...at 11:30 was version 0.8.5...now
> there is a 0.9.1 version??
Sherm Pendley wrote:
> Steve Holden <[EMAIL PROTECTED]> writes:
>
>> Sherm Pendley wrote:
>>> Gerardo Herzig <[EMAIL PROTECTED]> writes:
>>>
So..at 11:23 we got version 0.7.8...at 11:30 was version 0.8.5...now
there is a 0.9.1 version?? Have a coffe dude
>>> Sounds more to me like he ne
Steve Holden <[EMAIL PROTECTED]> writes:
> Sherm Pendley wrote:
>> Gerardo Herzig <[EMAIL PROTECTED]> writes:
>>
>>> So..at 11:23 we got version 0.7.8...at 11:30 was version 0.8.5...now
>>> there is a 0.9.1 version?? Have a coffe dude
>>
>> Sounds more to me like he needs to lay off the coffee, o
Sherm Pendley wrote:
> Gerardo Herzig <[EMAIL PROTECTED]> writes:
>
>> So..at 11:23 we got version 0.7.8...at 11:30 was version 0.8.5...now
>> there is a 0.9.1 version?? Have a coffe dude
>
> Sounds more to me like he needs to lay off the coffee, or at least switch
> to decaffeinated for a while
Gerardo Herzig <[EMAIL PROTECTED]> writes:
> So..at 11:23 we got version 0.7.8...at 11:30 was version 0.8.5...now
> there is a 0.9.1 version?? Have a coffe dude
Sounds more to me like he needs to lay off the coffee, or at least switch
to decaffeinated for a while. :-)
sherm--
--
Web Hosting b
Oleg Broytmann wrote:
>Hello!
>
>I'm pleased to announce the 0.9.1 release of SQLObject.
>
>
>What is SQLObject
>=
>
>SQLObject is an object-relational mapper. Your database tables are described
>as classes, and rows are instances of those classes. SQLObject is meant to be
>easy
> For reasons others will know, there are different branches to the
> SQLObject project. I think, analogously, python still has an active 2.4
> branch, if that helps make sense of maintaining branches based on
> versions. I'm not sure why the announcements aren't bundled into one
> because just abo
[EMAIL PROTECTED] wrote:
> Why was this released 3 times with different version numbers in less
> than an hour?
>
> Mike
>
For reasons others will know, there are different branches to the
SQLObject project. I think, analogously, python still has an active 2.4
branch, if that helps make sense
On May 10, 10:25 am, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I'm pleased to announce the 0.9.0 release of SQLObject, the first stable
> release of the 0.9 branch.
>
> What is SQLObject
> =
>
> SQLObject is an object-relational mapper. Your database tables are describ
Oleg Broytmann <[EMAIL PROTECTED]> writes:
> * Fixed sqlbuilder - .startswith(), .endswith() and .contains() assumed
> their parameter must be a string; now you can pass an SQLExpression:
> Table.q.name.contains(func.upper('a')), for example.
Oleg,
this made me think: is it possible to call
Larry Bates <[EMAIL PROTECTED]> writes:
> WOW! Went from 0.7.4 to 0.8.1 in the span of only 23 minutes!
There are two branches: 0.7 and 0.8. So, there were two releases.
--
Jorge Godoy <[EMAIL PROTECTED]>
--
http://mail.python.org/mailman/listinfo/python-list
Oleg Broytmann wrote:
> Hello!
>
> I'm pleased to announce the 0.8.1 release of SQLObject.
>
>
> What is SQLObject
> =
>
> SQLObject is an object-relational mapper. Your database tables are described
> as classes, and rows are instances of those classes. SQLObject is meant to
Oleg Broytmann wrote:
> Hello!
>
> I'm pleased to announce the 0.8.0b2 release of SQLObject.
>
>
> What is SQLObject
> =
>
> SQLObject is an object-relational mapper. Your database tables are described
> as classes, and rows are instances of those classes. SQLObject is meant t
Robert Hicks said the following on 22.1.2007 21:02:
> Where is Oracle support?
>
What about DB2 UDB and DB2/400 >:o
--
Dejan Rodiger - PGP ID 0xAC8722DC
Delete wirus from e-mail address
--
http://mail.python.org/mailman/listinfo/python-list
Where is Oracle support?
--
http://mail.python.org/mailman/listinfo/python-list
Daniel Nogradi wrote:
> Since I'm starting to use sqlobject right now, if there is a
> similar ORM tool that is comparable but up to date and actively
> developed, that would be an option too. (Things like SQLAlchemy are
> wy to complicated and complex for my needs. :))
Perhaps not really an a
> > To my knowledge, the 0.8.x series is the current line of development, and
> > has
> > made major progress over the previous versions. What makes you think it will
> > be stopped developing? And where does a sqlobject2 come from?
>
> http://www.sqlobject.org/2/
Yes, that's what I meant. The we
"Diez B. Roggisch" <[EMAIL PROTECTED]> writes:
> To my knowledge, the 0.8.x series is the current line of development, and has
> made major progress over the previous versions. What makes you think it will
> be stopped developing? And where does a sqlobject2 come from?
http://www.sqlobject.org/2/
Daniel Nogradi schrieb:
> Hi list,
>
> I get loads of DeprecationWarnings while using sqlobject 0.8.0b1 with
> python 2.5. Does this mean that the sqlobject project is not very up
> to date? Or should I just ignore them and happily use it? In general,
> what's the status of sqlobject, will it be d
Oracle?
Robert
--
http://mail.python.org/mailman/listinfo/python-list
Bruno Desthuilliers wrote:
> lazaridis_com wrote:
> > Bruno Desthuilliers wrote:
> >> lazaridis_com wrote:
> >>> Ο/Η Bruno Desthuilliers έγραψε:
> lazaridis_com wrote:
> > John Salerno wrote:
> >> Are there any major differences between these two? It seems they can
> >> both be us
alex23 wrote:
> lazaridis_com wrote:
> > The "persist case" evaluates python persistency systems (or
> > mechanisms), and will show my personal preference:
>
> Do you feel that evaluating-for-evaluation's-sake produces a more
> measured understanding of the value of a product than that taken from
>
lazaridis_com wrote:
> Bruno Desthuilliers wrote:
>> lazaridis_com wrote:
>>> Ο/Η Bruno Desthuilliers έγραψε:
lazaridis_com wrote:
> John Salerno wrote:
>> Are there any major differences between these two? It seems they can
>> both be used with TurboGears, and SQLAlchemy with Djan
lazaridis_com wrote:
> The "persist case" evaluates python persistency systems (or
> mechanisms), and will show my personal preference:
Do you feel that evaluating-for-evaluation's-sake produces a more
measured understanding of the value of a product than that taken from
its use in, say, actual de
Bruno Desthuilliers wrote:
> lazaridis_com wrote:
> > Ο/Η Bruno Desthuilliers έγραψε:
> >> lazaridis_com wrote:
> >>> John Salerno wrote:
> Are there any major differences between these two? It seems they can
> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> wond
lazaridis_com wrote:
> Ο/Η Bruno Desthuilliers έγραψε:
>> lazaridis_com wrote:
>>> John Salerno wrote:
Are there any major differences between these two? It seems they can
both be used with TurboGears, and SQLAlchemy with Django. I'm just
wondering what everyone's preference is, and
Ο/Η Bruno Desthuilliers έγραψε:
> lazaridis_com wrote:
> > John Salerno wrote:
> >> Are there any major differences between these two? It seems they can
> >> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> >> wondering what everyone's preference is, and why, and if there are e
lazaridis_com wrote:
> John Salerno wrote:
>> Are there any major differences between these two? It seems they can
>> both be used with TurboGears, and SQLAlchemy with Django. I'm just
>> wondering what everyone's preference is, and why, and if there are even
>> more choices for ORM.
>>
>> Thanks.
John Salerno wrote:
> Are there any major differences between these two? It seems they can
> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> wondering what everyone's preference is, and why, and if there are even
> more choices for ORM.
>
> Thanks.
You can review the Persit Ca
Jorge Vargas wrote:
> On 8/31/06, John Salerno <[EMAIL PROTECTED]> wrote:
>> Are there any major differences between these two? It seems they can
>> both be used with TurboGears, and SQLAlchemy with Django. I'm just
>> wondering what everyone's preference is, and why, and if there are even
>> more
"Jorge Vargas" <[EMAIL PROTECTED]> writes:
> for example SA wins at using an existing db
> but SO wins at not worring about the db structure
That's not entirely true. Some things are impossible with SQL Object alone.
You have to, at least, make use of sqlbuilder. And these aren't hard things,
m
On 8/31/06, John Salerno <[EMAIL PROTECTED]> wrote:
> Are there any major differences between these two? It seems they can
> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> wondering what everyone's preference is, and why, and if there are even
> more choices for ORM.
>
they us
"BJörn Lindqvist" <[EMAIL PROTECTED]> writes:
> I think this post by the author of SQLAlchemy perfectly summarizes the
> differences between the two ORMs:
>
> http://article.gmane.org/gmane.comp.python.sqlalchemy.user/1072/
And ActiveMapper is working to some extent better than it was by the time
I think this post by the author of SQLAlchemy perfectly summarizes the
differences between the two ORMs:
http://article.gmane.org/gmane.comp.python.sqlalchemy.user/1072/
--
mvh Björn
--
http://mail.python.org/mailman/listinfo/python-list
John Salerno wrote:
> Adam Jones wrote:
>
> > I think SA's extra flexability
> > is worth the effort.
>
> Thanks for the reply. Do you mean in the above quote that SA is a little
> more complicated than SO?
Yes, it is. To avoid the technical issues involved the complication can
be summarized as:
John Salerno a écrit :
> Are there any major differences between these two?
Yes. SQLAlchemy is, mainly, a very higher-level DB-API that makes
working with a RDBMS almost transparent (no embedded SQL unless you
really wants to) without trying to pretend there's no RDBMS nor forcing
you into ORM
John Salerno wrote:
> Thanks for the reply. Do you mean in the above quote that SA is a little
> more complicated than SO?
Don't be afraid to download them and try their respective tutorials.
Each one would take about an hour and then you'd have a feel for
yourself. I agree with adam that SQLAl
John Salerno wrote:
> Are there any major differences between these two? It seems they can
> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> wondering what everyone's preference is, and why, and if there are even
> more choices for ORM.
I just finished surfing both websites l
Adam Jones wrote:
> I think SA's extra flexability
> is worth the effort.
Thanks for the reply. Do you mean in the above quote that SA is a little
more complicated than SO?
--
http://mail.python.org/mailman/listinfo/python-list
John Salerno wrote:
> Are there any major differences between these two? It seems they can
> both be used with TurboGears, and SQLAlchemy with Django. I'm just
> wondering what everyone's preference is, and why, and if there are even
> more choices for ORM.
>
> Thanks.
Currently most of my work i
Hi Jake,
When establishing a new connection using sqlobject, there is a param
called cache that has a default val of True. See
http://sqlobject.org/SQLObject.html#declaring-the-class
For more info, potential gotchas, etc, check out
http://wiki.sqlobject.org/connections.html
http://pythonpaste.
No - I want autoCommit to be false. It defaults to true. SQLObject's
documentation says to leave the value blank for false, and to specify
any non-blank value for true.
Is the SQLObject documentation wrong? Should I specify autoCommit=0?
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
> I'm trying to connect to a mysql database, with autoCommit and caching
> off, and I'm trying to create a transaction. Why does this blow up?
As the traceback is telling you, your connectionString is missing the
actual values. Not sure about the cache parameter but:
conne
[EMAIL PROTECTED] si è profuso/a a scrivere su comp.lang.python tutte
queste elucubrazioni:
> Hello. Does SQLObject provide connection pooling? If so, is it
> automatic or do I have to do something to manage it? If not, how do
> people generally solve this problem?
I think you will have bette
[EMAIL PROTECTED] wrote:
> Does anyone see what I'm doing wrong?
Using MySQL? Are you aware that MySQL doesn't support transaction
handling with COMMIT and ROLLBACK in all configurations. It depends
on your MySQL version and what table backend you are using.
The Python DB-API states that autocomm
qvx wrote:
> "autocommit off" attempt:
>
> connection_string = 'sqlite:/' + db_filename +'?autoCommit=0'
>
> "no select" attempt:
>
> t1 = T1(id=t1id, col1=r.col1, ...)
I changed :
conn_string = 'sqlite:/' + db_datoteka +'?autoCommit=0'
conn = connectionForURI(conn_string)
SQL
Skip is correct, they're somewhat different:
SQLObject is an 'ORM' or 'Object-Relational Mapping', meaning that it
allows you to handle everything related to the database with objects.
The table handles are objects, the result set is an object, the
individual rows in a result set are objects with
yaffa> i have a python script that scrapes contents from an html file
yaffa> and i would like to have the script write values to a mysql db.
yaffa> do you recommend i go with the sqlobject or the mysqldb module?
They are really quite different beasts. You'll have to consider your
requ
69 matches
Mail list logo
