Similarly, precision is in place of maxLength. Logically, getMaxLength 
for decimal returns null and getPrecision returns precision, but they 
are stored in the same systable column.

Also, I found the code block that is currently infinite looping. Looking 
into why it's looping.

On 02/26/2013 04:04 PM, James Taylor wrote:
>
> In src/main/java/com/salesforce/phoenix/schema/PColumnDecimalImpl.java:
>
> > +        PName columnName = new PNameImpl(columnNameBytes);
> > +        byte[] familyNameBytes = Bytes.readByteArray(input);
> > +        PName familyName = familyNameBytes.length == 0 ? null : new PNameImpl(familyNameBytes);
> > +        PDataType dataType = PDataType.values()[WritableUtils.readVInt(input)];
> > +        int precision = WritableUtils.readVInt(input);
> > +        boolean nullable = input.readBoolean();
> > +        int position = WritableUtils.readVInt(input);
> > +        int scale = WritableUtils.readVInt(input);
> > +        init(columnName, familyName, dataType, null, nullable, position);
> > +        this.precision = precision;
> > +        this.scale = scale;
> > +    }
> > +
> > +    @Override
> > +    public void write(DataOutput output) throws IOException {
> > +        Bytes.writeByteArray(output, getName().getBytes());
>
> Same here
>
> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/forcedotcom/phoenix/pull/72/files#r3163711>.
>