Development

#3105 (unsigned property not set by propel-build-*)

You must first sign up to be able to contribute.

Ticket #3105 (new defect)

Opened 4 months ago

Last modified 4 months ago

unsigned property not set by propel-build-*

Reported by: donet Assigned to: fabien
Priority: major Milestone:
Component: model Version: 1.0.12
Keywords: unsigned Cc:
Qualification: Unreviewed

Description

Hi,

I'm working on my first implementation of symfony and I couldn't find a solution to this problem:

in my schema.yml fil I have this table definition:

propel:

area:

_attributes: { phpName: Area } id: varchar(12) name: varchar(32) level: { type: tinyint, unsigned: true, index: true }

but after I run propel-build-model + propel-build-sql there is not trace of the unsigned property, the sql to create the db doesn't contains that column property at all. I think it can be a bug since in all the docs I found that definitions seems to be correct.

Change History

03/13/08 12:38:39 changed by FabianLange

that seems to be a propel limitation. perhaps because it cannot be mapped to a php datatype appropriatly

03/27/08 10:51:25 changed by Eric.Lemoine

  • priority changed from minor to major.
  • version changed from 1.0.7 to 1.0.12.

I think it is a major issue since it affects for example all the auto_increment id columns which are commonly unsigned integers. Being signed integers it reduces by half the number of rows we will be able to use.

It also affects the storage of network addresses in unsigned integer columns (MySQL manual recommands to use unsigned integer : http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html#function_inet-aton).

We also often use unsigned tinyint to be able to store up to 512 positives values. With signed tinyint instead it reduces the storage to 256 positives values.