sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] DateCol format on default

[Gustavo A. D. <gus...@gm...>]

Oleg!

Thanks for reply. Yeah, but is ok since finally I don't care how is stored
in the DB since I can parse it later (sometimes I ask questions in lists,
forums and in a few minutes I reply myself with a solution... sorry :P)

About signature: lol (If true I didn't know :P)

Thanks!

--

Gustavo A. Díaz
GDNet - www.gdnet.com.ar
"Servicios TI para tus necesidades"

2015-08-26 14:26 GMT-03:00 Oleg Broytman <ph...@ph...>:

> Hi!
>
> On Wed, Aug 26, 2015 at 02:07:38PM -0300, "Gustavo A. D??az" <
> gus...@gm...> wrote:
> > Is there anyway to change for date format on DateCol default value?
> >
> > I use DateCol(default=datetime.strftime(datetime.now(), '%d-%m-%Y') but
> > does not work:
> >
> > unhandled formencode.api.Invalid "expected a date/time string of the
> > '%Y-%m-%d' format in the DateTimeCol 'modified', got <class 'str'>
> > '26-08-2015' instead"
>
>    The problem is that the code that's used to parse user input is also
> used to parse output from the backend, so if you want to change the
> format yo have to change it at the DB level too. And then you have to
> change DateTimeConverter to pass date/time strings to the backing in the
> proper format.
>    See the discussion and some examples at
> https://github.com/sqlobject/sqlobject/issues/114
>
>    Your best bet, I think, is to parse d/t strings yourself and pass
> date/datetime instances to your column(s).
>
> > Thanks!
> >
> > --
>     ^ You have forgotten a space here; signatures are separated by two
> dashes and a space. (-:
>
> > Gustavo A. D??az
> > GDNet - www.gdnet.com.ar
> > "Servicios TI para tus necesidades"
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] DateCol format on default

[Oleg B. <ph...@ph...>]

Hi!

On Wed, Aug 26, 2015 at 02:07:38PM -0300, "Gustavo A. D??az" <gus...@gm...> wrote:
> Is there anyway to change for date format on DateCol default value?
> 
> I use DateCol(default=datetime.strftime(datetime.now(), '%d-%m-%Y') but
> does not work:
> 
> unhandled formencode.api.Invalid "expected a date/time string of the
> '%Y-%m-%d' format in the DateTimeCol 'modified', got <class 'str'>
> '26-08-2015' instead"

   The problem is that the code that's used to parse user input is also
used to parse output from the backend, so if you want to change the
format yo have to change it at the DB level too. And then you have to
change DateTimeConverter to pass date/time strings to the backing in the
proper format.
   See the discussion and some examples at
https://github.com/sqlobject/sqlobject/issues/114

   Your best bet, I think, is to parse d/t strings yourself and pass
date/datetime instances to your column(s).

> Thanks!
> 
> --
    ^ You have forgotten a space here; signatures are separated by two
dashes and a space. (-:

> Gustavo A. D??az
> GDNet - www.gdnet.com.ar
> "Servicios TI para tus necesidades"

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] DateCol format on default

[Gustavo A. D. <gus...@gm...>]

Forget this question, I just stored with default=DateTimeCol.now and when
read it, just formated with datetime.strftime.

Thanks!

--

Gustavo A. Díaz
GDNet - www.gdnet.com.ar
"Servicios TI para tus necesidades"

2015-08-26 14:07 GMT-03:00 Gustavo A. Díaz <gus...@gm...>:

> Hi,
>
> Is there anyway to change for date format on DateCol default value?
>
> I use DateCol(default=datetime.strftime(datetime.now(), '%d-%m-%Y') but
> does not work:
>
> unhandled formencode.api.Invalid "expected a date/time string of the
> '%Y-%m-%d' format in the DateTimeCol 'modified', got <class 'str'>
> '26-08-2015' instead"
>
> Thanks!
>
> --
>
> Gustavo A. Díaz
> GDNet - www.gdnet.com.ar
> "Servicios TI para tus necesidades"
>

[SQLObject] DateCol format on default

[Gustavo A. D. <gus...@gm...>]

Hi,

Is there anyway to change for date format on DateCol default value?

I use DateCol(default=datetime.strftime(datetime.now(), '%d-%m-%Y') but
does not work:

unhandled formencode.api.Invalid "expected a date/time string of the
'%Y-%m-%d' format in the DateTimeCol 'modified', got <class 'str'>
'26-08-2015' instead"

Thanks!

--

Gustavo A. Díaz
GDNet - www.gdnet.com.ar
"Servicios TI para tus necesidades"

Re: [SQLObject] querying with foreign key

[Oleg B. <ph...@ph...>]

Hi!

On Wed, Jun 24, 2015 at 04:13:21PM +0000, Taia Modlin <tai...@ya...> wrote:
> Hello,
> I was wondering if it is possible to filter a table based on a field from it's foreign key.
> Thanks

   There are two ways: simple and efficient. Let's see an example:

from sqlobject import *

__connection__ = "sqlite:/:memory:?debug=1&debugOutput=1"

class Test1(SQLObject):
    name = StringCol()

class Test2(SQLObject):
    name = StringCol()
    test1 = ForeignKey("Test1")

Test1.createTable()
Test2.createTable()

test1 = Test1(name="one")
test2 = Test2(name="One", test1=test1)

test1 = Test1(name="two")
test2 = Test2(name="Two", test1=test1)

# Simple way: run through all rows
for row in Test2.select():
    if row.test1.name == "one":
        print row.name

# Efficient way: do join
for row in Test2.select((Test2.q.test1==Test1.q.id) & (Test1.q.name=="one")):
    print row

   The join produces the following SQL:

SELECT test2.id, test2.name, test2.test1_id FROM test1, test2 WHERE (((test2.test1_id) = (test1.id)) AND ((test1.name) = ('one')))

   The advantage of join is efficiency, the disadvantage is that you
have to write it manually even if SQLObject has got enough information
to do it for you.

   See also a short note on using .throughTo magic attribute:

http://sqlobject.org/SelectResults.html#throughto-join-name-and-throughto-foreign-key-name

   but it doesn't apply to my example.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] querying with foreign key

[Taia M. <tai...@ya...>]

Hello,
I was wondering if it is possible to filter a table based on a field from it's foreign key.
Thanks

[SQLObject] SQLObject 2.2.0b1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 2.2.0b1, the first beta of the upcoming
release of branch 2.2 of SQLObject.


What's new in SQLObject
=======================

Features & Interface
--------------------

* Add function col.use_microseconds(True/False). Default is to use
  microseconds (True).

* For MSSQL use datetime2(6) and time(6) columns.

Minor features
--------------

* Minor refactoring to pave the way to Python 3 was merged from
  `SQLObject 1.6.7`_.

Bugfixes
--------

* Fix a bug: mxDateTime doesn't support microseconds; %s in mxDateTime
  format means ticks.

Contributor for this release is Andrew Ziem.

For a more complete list, please see the news:
http://sqlobject.org/News.html


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 to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6 or 2.7 is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.2.0b1dev-20150619

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Versioning with SQLRelatedJoin?

[Alex S. <as...@ti...>]

Thanks Oleg!
That makes sense.  I just wanted to make sure I wasn't missing anything 
before I went ahead and did that.

cheers,
Alex


On 6/9/15 5:37 AM, Oleg Broytman wrote:
> Hello!
>
> On Mon, Jun 08, 2015 at 04:46:08PM -0700, aseiden <as...@ti...> wrote:
>> Is it possible to combine SQLObject Versioning with a SQLRelatedJoin?
>     I don't believe it's possible, at least possible using simple
> approach. The problem is that versioned data is copied to a separate
> versioning table while joins retain pointers between main tables.
>
>     I think your best bet is to implement your own versioning in the main
> table (Cart, in your case).
>
> Oleg.

Re: [SQLObject] Versioning with SQLRelatedJoin?

[Oleg B. <ph...@ph...>]

Hello!

On Mon, Jun 08, 2015 at 04:46:08PM -0700, aseiden <as...@ti...> wrote:
> Is it possible to combine SQLObject Versioning with a SQLRelatedJoin?

   I don't believe it's possible, at least possible using simple
approach. The problem is that versioned data is copied to a separate
versioning table while joins retain pointers between main tables.

   I think your best bet is to implement your own versioning in the main
table (Cart, in your case).

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Versioning with SQLRelatedJoin?

[aseiden <as...@ti...>]

Is it possible to combine SQLObject Versioning with a SQLRelatedJoin?

Here's what I'm trying to do:  I have a many-to-many relationship 
between two classes, "Asset" and "Cart".  A Cart can have a bunch of 
Assets, and Assets can belong to more than one cart.

I'd like to be able to version changes to the assets that are in the 
cart (i.e. the cart.assets field) as well as the other

Here's a simplified version of what I'm doing:

#!/usr/bin/env python

import os, time, datetime
from sqlobject import *
from sqlobject.versioning import Versioning

class Asset(SQLObject):
     name = StringCol(unique=True, length=255)
     author = StringCol(length=20, default=os.getenv('USER'))
     date = DateTimeCol(default=DateTimeCol.now)
     notes = StringCol(default='')
     savedcarts = SQLRelatedJoin('Cart')


class Cart(SQLObject):
     """ A saved list of AssetItems. Usually created in RepoBrowse. """
     name = StringCol(unique=True, length=255)
     author = StringCol(length=20, default=os.getenv('USER'))
     date = DateTimeCol(default=DateTimeCol.now)
     notes = StringCol(default='')
     assets = SQLRelatedJoin("Asset", addRemoveName="Asset")

     versions = Versioning()

     def dumpVersions(self):
         for i, vers in enumerate(self.versions):
             allAssetNames = [ass.name for ass in vers.assets]
             print "#%d %s %-40.40s %s     Assets: %s"%(i, vers.name, 
vers.notes, vers.date, ','.join(allAssetNames))


if __name__ == '__main__':
     # Make DB
     dbname = os.path.abspath("joinV.sq3")
     os.remove(dbname)
     dburl = 'sqlite://%s'%dbname
     connection = connectionForURI(dburl)
     sqlhub.processConnection = connection

     Asset.createTable(ifNotExists=True)
     Cart.createTable(ifNotExists=True)

     # Make some assets
     assFoo = Asset(name="Foo")
     assBar = Asset(name="Bar")
     assBaz = Asset(name="Baz")
     assAck = Asset(name="Ack")

     # Make a cart
     cart = Cart(name="Savedcart1")

     for i, ass in enumerate([assFoo, assBar, assBaz, assAck]):
         cart.addAsset(ass)
         cart.notes='submission %d--added "%s"'%(i, ass.name)

     cart.dumpVersions()



This outputs:

#0 Savedcart1 2015-06-08 16:36:59     Assets: Foo,Bar,Baz,Ack
#1 Savedcart1 submission 0--added "Foo" 2015-06-08 16:36:59     Assets: 
Foo,Bar,Baz,Ack
#2 Savedcart1 submission 1--added "Bar" 2015-06-08 16:36:59     Assets: 
Foo,Bar,Baz,Ack
#3 Savedcart1 submission 2--added "Baz" 2015-06-08 16:36:59     Assets: 
Foo,Bar,Baz,Ack

What I'd like to see is #0 have vers.assets only contain "Foo", #1 have 
only "Foo" and "Bar", etc.
Is this possible with SQLObject's versioning?

Thanks much!
Alex Seiden

p.s. I'm using Linux (CentOS 6.6), python 2.7, and SQLObject 1.6.  I 
would update to a more recent SQLObject if it would matter, but I didn't 
see anything in the release notes that seemed relevant.  And FWIW, my 
'real' app uses mysql, but sqlite was easier for the example.

[SQLObject] SQLObject 3.0.0a1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 3.0.0a1, the first alpha of the upcoming
release of branch 3.0 of SQLObject.


What's new in SQLObject
=======================

Features
--------

* Support for Python 2 and Python 3 with one codebase!
  (Python version >= 3.4 currently required.)

Minor features
--------------

* Use fdb adapter for Firebird.

* PyDispatcher (>=2.0.4) was made an external dependency.

Development
-----------

* Source code was made flake8-clean.

Documentation
-------------

* Documentation is published at http://sqlobject.readthedocs.org/ in
  Sphinx format.

Contributors for this release are Ian Cordasco, Neil Muller,
Lukasz Dobrzanski, Gregor Horvath.

For a more complete list, please see the news:
http://sqlobject.org/News.html


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 to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6, 2.7 or 3.4+ is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/3.0.0a1dev-20150327

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Oleg B. <ph...@ph...>]

On Thu, Mar 26, 2015 at 07:12:46PM -0500, Ian Cordasco <gra...@gm...> wrote:
> On Thu, Mar 26, 2015 at 6:55 PM, Oleg Broytman <ph...@ph...> wrote:
> 
> > On Thu, Mar 26, 2015 at 06:45:21PM -0500, Ian Cordasco <
> > gra...@gm...> wrote:
> > > On Thu, Mar 26, 2015 at 6:34 PM, Oleg Broytman <ph...@ph...> wrote:
> > >
> > > > On Fri, Mar 27, 2015 at 12:05:53AM +0100, Oleg Broytman <
> > ph...@ph...>
> > > > wrote:
> > > > > On Thu, Mar 26, 2015 at 05:53:19PM -0500, Ian Cordasco <
> > > > gra...@gm...> wrote:
> > > > > > > > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...>
> > wrote:
> > > > > > > > > Hi! All tests are green. What's next?
> > > > >
> > > > > > An alpha release might help us get some beta testers. Maybe create
> > a
> > > > > > 3.0.0a1 that people can then pip install?
> > > > >
> > > > >    Nice idea, will do it!
> > > >
> > > >    Sorry, I was too haste. I need python 3.4 on my system to release
> > > > SQLObject for Python 3 ;-) so I have to update my stable Debian to
> > > > testing. I wanted to do that anyway so I hope to upgrade at the
> > weekend.
> > >
> > > You don't need Python 3 to release it. You just need to make sure that
> > the
> > > correct classifier is there (not that pip cares) and then do a `python
> > > setup.py sdist`. If you want to release a wheel, you can do `python
> > > setup.py bdist_wheel --universal` to signal that it works on Python 2 and
> > > Python 3. (That can be done from either Python 2 or Python 3 so you don't
> > > need 3.4 installed.)
> >
> >    Aha, that's better, thank you!
> >
> >    Wheels don't include .pyc/.pyo files? They are very much
> > version-specific, you know.
> >
> If I recall correctly, wheels do not contain py[co] files at all. They're
> just a superiour packaging format and they are must faster than source
> distributions.

   Ok, will try.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Ian C. <gra...@gm...>]

On Thu, Mar 26, 2015 at 6:55 PM, Oleg Broytman <ph...@ph...> wrote:

> On Thu, Mar 26, 2015 at 06:45:21PM -0500, Ian Cordasco <
> gra...@gm...> wrote:
> > On Thu, Mar 26, 2015 at 6:34 PM, Oleg Broytman <ph...@ph...> wrote:
> >
> > > On Fri, Mar 27, 2015 at 12:05:53AM +0100, Oleg Broytman <
> ph...@ph...>
> > > wrote:
> > > > On Thu, Mar 26, 2015 at 05:53:19PM -0500, Ian Cordasco <
> > > gra...@gm...> wrote:
> > > > > > > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...>
> wrote:
> > > > > > > > Hi! All tests are green. What's next?
> > > >
> > > > > An alpha release might help us get some beta testers. Maybe create
> a
> > > > > 3.0.0a1 that people can then pip install?
> > > >
> > > >    Nice idea, will do it!
> > >
> > >    Sorry, I was too haste. I need python 3.4 on my system to release
> > > SQLObject for Python 3 ;-) so I have to update my stable Debian to
> > > testing. I wanted to do that anyway so I hope to upgrade at the
> weekend.
> >
> > You don't need Python 3 to release it. You just need to make sure that
> the
> > correct classifier is there (not that pip cares) and then do a `python
> > setup.py sdist`. If you want to release a wheel, you can do `python
> > setup.py bdist_wheel --universal` to signal that it works on Python 2 and
> > Python 3. (That can be done from either Python 2 or Python 3 so you don't
> > need 3.4 installed.)
>
>    Aha, that's better, thank you!
>
>    Wheels don't include .pyc/.pyo files? They are very much
> version-specific, you know.
>
>
If I recall correctly, wheels do not contain py[co] files at all. They're
just a superiour packaging format and they are must faster than source
distributions.

Re: [SQLObject] Python 3

[Oleg B. <ph...@ph...>]

On Thu, Mar 26, 2015 at 06:45:21PM -0500, Ian Cordasco <gra...@gm...> wrote:
> On Thu, Mar 26, 2015 at 6:34 PM, Oleg Broytman <ph...@ph...> wrote:
> 
> > On Fri, Mar 27, 2015 at 12:05:53AM +0100, Oleg Broytman <ph...@ph...>
> > wrote:
> > > On Thu, Mar 26, 2015 at 05:53:19PM -0500, Ian Cordasco <
> > gra...@gm...> wrote:
> > > > > > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> > > > > > > Hi! All tests are green. What's next?
> > >
> > > > An alpha release might help us get some beta testers. Maybe create a
> > > > 3.0.0a1 that people can then pip install?
> > >
> > >    Nice idea, will do it!
> >
> >    Sorry, I was too haste. I need python 3.4 on my system to release
> > SQLObject for Python 3 ;-) so I have to update my stable Debian to
> > testing. I wanted to do that anyway so I hope to upgrade at the weekend.
> 
> You don't need Python 3 to release it. You just need to make sure that the
> correct classifier is there (not that pip cares) and then do a `python
> setup.py sdist`. If you want to release a wheel, you can do `python
> setup.py bdist_wheel --universal` to signal that it works on Python 2 and
> Python 3. (That can be done from either Python 2 or Python 3 so you don't
> need 3.4 installed.)

   Aha, that's better, thank you!

   Wheels don't include .pyc/.pyo files? They are very much
version-specific, you know.

> Cheers,
> Ian

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Ian C. <gra...@gm...>]

On Thu, Mar 26, 2015 at 6:34 PM, Oleg Broytman <ph...@ph...> wrote:

> On Fri, Mar 27, 2015 at 12:05:53AM +0100, Oleg Broytman <ph...@ph...>
> wrote:
> > On Thu, Mar 26, 2015 at 05:53:19PM -0500, Ian Cordasco <
> gra...@gm...> wrote:
> > > > > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> > > > > > Hi! All tests are green. What's next?
> >
> > > An alpha release might help us get some beta testers. Maybe create a
> > > 3.0.0a1 that people can then pip install?
> >
> >    Nice idea, will do it!
>
>    Sorry, I was too haste. I need python 3.4 on my system to release
> SQLObject for Python 3 ;-) so I have to update my stable Debian to
> testing. I wanted to do that anyway so I hope to upgrade at the weekend.
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>


You don't need Python 3 to release it. You just need to make sure that the
correct classifier is there (not that pip cares) and then do a `python
setup.py sdist`. If you want to release a wheel, you can do `python
setup.py bdist_wheel --universal` to signal that it works on Python 2 and
Python 3. (That can be done from either Python 2 or Python 3 so you don't
need 3.4 installed.)

Cheers,
Ian

Re: [SQLObject] Python 3

[Oleg B. <ph...@ph...>]

On Fri, Mar 27, 2015 at 12:05:53AM +0100, Oleg Broytman <ph...@ph...> wrote:
> On Thu, Mar 26, 2015 at 05:53:19PM -0500, Ian Cordasco <gra...@gm...> wrote:
> > > > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> > > > > Hi! All tests are green. What's next?
> 
> > An alpha release might help us get some beta testers. Maybe create a
> > 3.0.0a1 that people can then pip install?
> 
>    Nice idea, will do it!

   Sorry, I was too haste. I need python 3.4 on my system to release
SQLObject for Python 3 ;-) so I have to update my stable Debian to
testing. I wanted to do that anyway so I hope to upgrade at the weekend.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Oleg B. <ph...@ph...>]

On Thu, Mar 26, 2015 at 05:53:19PM -0500, Ian Cordasco <gra...@gm...> wrote:
> > > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> > > > Hi! All tests are green. What's next?

> An alpha release might help us get some beta testers. Maybe create a
> 3.0.0a1 that people can then pip install?

   Nice idea, will do it!

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Ian C. <gra...@gm...>]

On Mar 26, 2015 4:11 PM, "Oleg Broytman" <ph...@ph...> wrote:
>
> On Thu, Mar 26, 2015 at 09:47:31PM +0200, Neil Muller <
drn...@gm...> wrote:
> > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> > > Hi! All tests are green. What's next?
> >
> > I'm currently working on converting a few small'ish programs I have to
> > use python 3 and sqlobject trunk, to see if that shows any lingering
> > issues.
>
>    Very well!
>
> > Unfortunately, I haven't been able to find a lot of time to
> > work on sqlobject over the last few weeks, so this hasn't been
> > proceeding as quickly as I'd hoped.
>
>    Ok, I see.
>
> > --
> > Neil Muller
> > drn...@gm...
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
>
------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub
for all
> things parallel software development, from weekly thought leadership
blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss

An alpha release might help us get some beta testers. Maybe create a
3.0.0a1 that people can then pip install?

Re: [SQLObject] Python 3

[Oleg B. <ph...@ph...>]

On Thu, Mar 26, 2015 at 09:47:31PM +0200, Neil Muller <drn...@gm...> wrote:
> On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> > Hi! All tests are green. What's next?
> 
> I'm currently working on converting a few small'ish programs I have to
> use python 3 and sqlobject trunk, to see if that shows any lingering
> issues.

   Very well!

> Unfortunately, I haven't been able to find a lot of time to
> work on sqlobject over the last few weeks, so this hasn't been
> proceeding as quickly as I'd hoped.

   Ok, I see.

> -- 
> Neil Muller
> drn...@gm...

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Neil M. <drn...@gm...>]

On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> Hi! All tests are green. What's next?
>

I'm currently working on converting a few small'ish programs I have to
use python 3 and sqlobject trunk, to see if that shows any lingering
issues. Unfortunately, I haven't been able to find a lot of time to
work on sqlobject over the last few weeks, so this hasn't been
proceeding as quickly as I'd hoped.

-- 
Neil Muller
drn...@gm...

I've got a gmail account. Why haven't I become cool?

[SQLObject] Python 3

[Oleg B. <ph...@ph...>]

Hi! All tests are green. What's next?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 2.1.2 and 1.7.5

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce versions 2.1.2 and 1.7.5, minor feature releases of
of SQLObject.


What's new in SQLObject
=======================

* Use fdb adapter for Firebird.

Contributor for this release is Neil Muller.

For a more complete list, please see the news:
http://sqlobject.org/News.html


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 to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6 or 2.7 is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.1.2
https://pypi.python.org/pypi/SQLObject/1.7.5

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.6.6

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.6.6, a minor feature release of branch
1.6 of SQLObject.


What's new in SQLObject
=======================

* Use fdb adapter for Firebird.

Contributor for this release is Neil Muller.

For a more complete list, please see the news:
http://sqlobject.org/News.html


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 to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.5 or higher is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.6.6

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 2.1.1 and 1.7.4

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce minor bugfix releases 2.1.1 and 1.7.4.


What's new in SQLObject
=======================

* Minor fix in PostgresConnection: close the cursor and connection
  in _createOrDropDatabase even after an error.

Contributor for this release is Gregor Horvath.

For a more complete list, please see the news:
http://sqlobject.org/News.html


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 to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6 or 2.7 is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.1.1
https://pypi.python.org/pypi/SQLObject/1.7.4

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.6.5

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.6.5, a minor bugfix release of branch
1.6 of SQLObject.


What's new in SQLObject
=======================

* Minor fix in PostgresConnection: close the cursor and connection
  in _createOrDropDatabase even after an error.

Contributor for this release is Gregor Horvath.

For a more complete list, please see the news:
http://sqlobject.org/News.html


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 to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.5 or higher is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.6.5

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.