[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-09 Thread Jon Rosebaugh
On Jan 7, 2008 2:20 PM, Michael Bayer [EMAIL PROTECTED] wrote: 0.4.2b -- - sql - changed name of TEXT to Text since its a generic type; TEXT name is deprecated until 0.5. The upgrading behavior of String to Text when no length is present is also deprecated until

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-09 Thread Jorge Godoy
Jon Rosebaugh wrote: What are we supposed to do with Unicode? As far as I can tell, the Unicode type passes its defined length directly to the underlying string, so that a Unicode(30) column is turned into a VARCHAR(30) or the dialect equivalent. I may be able to determine that a particular

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-09 Thread Michael Schlenker
Jorge Godoy schrieb: Jon Rosebaugh wrote: What are we supposed to do with Unicode? As far as I can tell, the Unicode type passes its defined length directly to the underlying string, so that a Unicode(30) column is turned into a VARCHAR(30) or the dialect equivalent. I may be able to

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-09 Thread Michael Bayer
On Jan 9, 2008, at 3:33 AM, Jon Rosebaugh wrote: On Jan 7, 2008 2:20 PM, Michael Bayer [EMAIL PROTECTED] wrote: 0.4.2b -- - sql - changed name of TEXT to Text since its a generic type; TEXT name is deprecated until 0.5. The upgrading behavior of String to Text

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-08 Thread Michael Bayer
On Jan 7, 2008, at 7:02 PM, Mike Orr wrote: On Jan 7, 2008 12:20 PM, Michael Bayer [EMAIL PROTECTED] wrote: This is a bugfix release and is recommended for all users who are currently on 0.4.2 or 0.4.2a. You really should bump the version number after a version has been released. 'a'

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-08 Thread Michael Bayer
On Jan 8, 2008, at 3:43 AM, Mike Orr wrote: Generally a third-level number is a minor bugfix release. A second-level number indicates feature changes or backward incompatibilities. A first-level number indicates a major paradigm shift. the problem with 0.4.3, 0.4.4 etc. is that we

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-08 Thread Mike Orr
On Jan 8, 2008 1:13 AM, Michael Bayer [EMAIL PROTECTED] wrote: the problem with 0.4.3, 0.4.4 etc. is that we assign those numbers as milestones in trac, and we do have a notion of a set of features that will be slowly rolled out over the course of the 0.4 series. [nod] That makes sense if

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-07 Thread Mike Orr
On Jan 7, 2008 12:20 PM, Michael Bayer [EMAIL PROTECTED] wrote: This is a bugfix release and is recommended for all users who are currently on 0.4.2 or 0.4.2a. You really should bump the version number after a version has been released. 'a' and 'b' look like alpha and beta. I installed 0.4.2

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-07 Thread Michael Bayer
On Jan 7, 2008, at 7:02 PM, Mike Orr wrote: On Jan 7, 2008 12:20 PM, Michael Bayer [EMAIL PROTECTED] wrote: This is a bugfix release and is recommended for all users who are currently on 0.4.2 or 0.4.2a. You really should bump the version number after a version has been released. 'a'

[sqlalchemy] Re: SQLAlchemy 0.4.2b released

2008-01-07 Thread Mike Bernson
Mike You just need pick letter that are after release. Thing like p1 is greater then release from the egg docs. (A note about versions: the egg runtime system understands typical version numbering schemes, so it knows that versions like 1.2a1 and 1.2rc5 are actually older than the plain