<div dir="ltr">Here is the link to the relevant documentation section <a href="http://doc.ponyorm.com/entities.html#max-integer-number-size" target="_blank">http://doc.ponyorm.com/entities.html#max-integer-number-size</a></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 4:25 PM, Alexey Malashkevich <span dir="ltr"><<a href="mailto:alexeymalashkevich@gmail.com" target="_blank">alexeymalashkevich@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi all,</div><div><br></div><div>The main point of this release candidate was the deprecation of long type for attributes in Pony. This in necessary for compatibility of Pony code with both Python 2 and Python 3. We hope that after this release candidate we will be ready to finally release the version 0.6.</div><div><br></div><div>Deprecation of long type for attributes<br></div><div>----------------------------------------------------</div><div><br></div><div>Since the long type has gone in Python 3, the long type is deprecated in Pony now. Instead of long you should use the int type and specify the size option:</div><div><br></div><div> class MyEntity(db.Entity):</div><div> attr1 = Required(long) # deprecated</div><div> attr2 = Required(int, size=64) # new way for using BIGINT type in the database</div><div>See more information on this here.</div><div><br></div><div>Bug fixes</div><div>---------------</div><div><br></div><div>Fixed #18: Allow to specify `size` and `unsigned` for int type</div><div>Fixed #77: Discriminate Pony-generated fields in entities: Attribute.is_implicit field added</div><div>Fixed #83: Entity.get() should issue LIMIT 2 when non-unique criteria used for search</div><div>Fixed #84: executing db.insert() should turn off autocommit and begin transaction</div><div>Fixed #88: composite_index(*attrs) added to support non-unique composite indexes</div><div>Fixed #89: IN / NOT IN clauses works different with empty sequence</div><div>Fixed #90: Do not automatically add “distinct” if query.first() used</div><div>Fixed #91: document automatic “distinct” behaviour and also .without_distinct()</div><div>Fixed #92: without_distinct() and first() do not work together correctly</div><div><br></div><div>Regards,</div><div>Alexey</div></div>
</blockquote></div><br></div>