Re: [binarycloud-dev] QueryManager / Standards

[Alex B. <en...@tu...>]

>> Respective for the XML complement. So QueryManager can loop over
>> the indexed arrays and generate an asoc array like:
>> 
>> $buffer[rownumber] = array(
>>     "Name1" => Datafromverlongcolumn1,
>>     "Name" => Datafromverylongcolumn2
>> );
> 
> Forgot to mention this. Using this method makes fetching result metadata
> obsolete. That would reduce db load and saving time, I guess.
> 
> But the main point is to get around truncation.

Right, but isn't that a lot of work for not much benefit? And where to we
store the metadata, in the Entity definition?

<field>
    <name>LongMixedCaseFieldNameWithNoStandard</name>
    <short_name>LONGMIXED</short_name>
</field>

egh! :)

---

I rethought an earlier message, so:

    -I don't want QueryManager to 'enforce' any field naming or other
standards. I don't want enforcement anywhere in the system.
    -What I would like to enforce with scripts, etc is this:

    :: For modules to be distributed with binarycloud or available from the
(upcoming) module repository, you must:
            -Use field and table/entity names with less than 32 chars.
            -Use CAPS for all field and table/entity names.
            -Verify that your SQL & Schemas work with Oracle, MySQL, and
PostgreSQL.


Does that sounds reasonable to everyone?

_a