BigInt -> twice the same space required, I'am not sure that's why they exists.. sql.log -> indeed, could do it this way, but, why is everything else possible with the DAL (up to now)?
On 17 Nov 2012, at 14:09, Niphlod wrote: > > I know 2**31, I meant the value: 2147483648 :) > And while the IS_INT_IN_RANGE is fine for negative value (I am already using > it) that does not change the fact that is the column is not set as unsigned, > 2147483648 can't be saved. > > that's why there's bigint. > > For the deployment, no that's not a solution. We require à fully scripted > solution that may be deployed by maintenance guys without knowledge of what > they do at anytime. > And the models evolve between updates. > > That was what I was talking about. taking sql.log and script the database > creation/migrations will save you a lot of troubles if you're going to deploy > several db in multiple instances > > Just out of curiosity, why unsigned it not a default and simple parameter ? > (handled only if the backend handles) > > Because noone until now needed it. > > > -- > > > --
