Re: Long text fields

Hi Dawn,
I don't know whether this will help you or not, but in UniVerse, if I have a
long comment-type field, I have the user enter it in something like Notepad
(or read it in line-by-line from some file using READSEQ), then WRITESEQ the
data out to a uniquely-named file somwhere on the system, and store that
filename in the database.

Then, when I want to read it in again (for display or other functions), I
open the file and, using READSEQ, read it in line-by-line. I have a
subroutine as well that I can use to split/combine lines based on a
separator character(s) within the file (CHAR(254), CHAR(13),
CHAR(10):CHAR(13) combination, or whatever character(s) you want). The
subroutine can also work like the "T" format, separating lines at a
convenient place close to X characters and inserting a separator character.

Dave


"dawn" <dawnwolthuis@xxxxxxxxx> wrote in message
news:1131377262.366623.134490@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I'm planning to actually code (!) in openQM and UniData beginning in
> January. I'm doing design and experimenting now. In case you think
> I'm an old pickie and this should be a piece of cake for me, I'll
> confess that until now I have always had teams of people working for me
> in the pick arena, so I don't know what most pick developers know. (I
> did my time in heads-down development a coupla decades ago in CICS
> COBOL.)
>
> So now I have some very basic (no pun intended) questions, starting
> with this one.
>
> I have worked with a UniData product that has long text fields (such as
> comment fields) as multvalued with formats like 60T. If I want to
> pass the text as a full string without any value marks, I could replace
> the value marks with a space, but I would think I could define a long
> single-valued field instead to eliminate the need for that.
>
> 1. I haven't looked it up for any particular db, but is there a
> standard longest field across pick environments? (An actual dtabase
> storage restriction)
>
> I would like the database to work in openQM and UniData, but would also
> like it to be compatible with the others -- UniVerse, Revelation,
> jBASE, D3, UniVision if I ever made the application work with those.
>
> 2. I realize the FMT is for display, not storage size, but is there a
> maximum in the FMT in the dictionary, such as FMT(99999T)?
>
> 3. Are there performance implications if I make a long single-valued
> text field instead of multivalued short lines of text? Other
> implications?
>
> 4. These questions might not even be the right ones, so what do you
> consider to be "best practices" related to long text fields in an MV
> environment where the application code will be in languages other than
> DataBASIC (e.g. PHP), retrieving data using a dictionary definition.
>
> Thanks in advance for any help. --dawn
>


.

Relevant Pages

  • Re: A Tale of Two Unis
    ... Does Unidata have ... We publish our credit software on several flavors, Universe and ... UV dictionaries will do most ...
    (comp.databases.pick)
  • Re: One-To-One Relationships
    ... Most IT professionals are inclined to think that in defining the database they have given the one and only real picture of the world. ... the database schema will reflect one of the universes of discourse that is used by professionals in the field being modeled. ... Now unfortunately, the professionals that use another universe of discourse may very well use the same words, but with a different meaning. ... At the end of the day, the meaning of a database schema is determined by its user community, or better by the universe of discourse in which the user community takes part. ...
    (comp.databases.theory)
  • Re: A real world example
    ... In a relational database, ... things in the universe. ... someone's DNA sequence could be considered an individual property (though in ... Lynn is third in the queue, so if you say something about Lynn or if you say ...
    (comp.databases.theory)
  • Re: computational model of transactions
    ... that is called the universe of discourse. ... the only statements in a database that can change are those that ... The absence of a statement in the succeeding database state ... Otherwise it would mean a transaction is allowed to see ...
    (comp.databases.theory)
  • Re: computational model of transactions
    ... No, the circumstances underpinning a fact have changed, and the database ... that is called the universe of discourse. ... The absence of a statement in the succeeding database state ... Otherwise it would mean a transaction is allowed to see uncommitted ...
    (comp.databases.theory)