Frustrating documentation

[Balestrieri, John]

Thanks Ruslan, that was the info I was looking for. (I did perform a search,
but it was by the field class name, not the data type name -- cross indexing
or linking the two might be useful.)

John


On 10/1/08 12:00 PM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

> On 10/1/08 6:04 PM, "Balestrieri, John" <jbalestrieri at ap.org> wrote:
> 
> Hi John,
> 
>> I'm trying to track down a problem in a VDb that's cropped up between
>> versions 2.x and 3.x. It appears the values of VULong field types are being
>> lost/clipped. Being one to help myself, I headed over to Valentina kernel
>> documentation for VULong:
>> 
>> <http://www.valentina-db.com/dokuwiki/doku.php?id=paradigma:public:en:docume
>> ntation:api:vulong_class:vulong_class>
> 
> This is API document.
> 
>> Nothing there on precision. So where exactly is the precision of this data
>> type documented? I find a passing reference to it here:
>> 
> Sounds like you want see Kernel Manual.
> 
> <http://www.valentina-db.com/dokuwiki/doku.php?id=paradigma:public:en:docume
> ntation:vkernel:vfield:vfield>
>
> 
>> I recall clear from 1.x and 2.x days the documentation used to be
>> exceptional; it was very easy to find what was needed (as well,
>> documentation was available in offline format, which, IMHO, is essential for
>> mission-critical development where a third-party server cannot be relied
>> upon.)
> 
> In WIKI also easy to find.
> 
> You see field SEARCH on top left side?
>     type here ULONG and see results.
> 



The information contained in this communication is intended for the use
of the designated recipients named above. If the reader of this 
communication is not the intended recipient, you are hereby notified
that you have received this communication in error, and that any review,
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please 
notify The Associated Press immediately by telephone at +1-212-621-1898 
and delete this email. Thank you.
[IP_US_DISC]
msk dccc60c6d2c3a6438f0cf467d9a4938