Pervasive Community Site

Community Forum (formally DEVTALK) – Join the ever- growing Pervasive community in a lively, interactive e-nvironment where users can come together and discuss their choice of topics on Pervasive-based products.  Participants include Developers, Resellers, System Integrators, and End User and Pervasive team members.

Component Zone – Download the latest utilities and tools posted by third-party vendors.  The Zone is your quick stop for getting the latest tools our partners have to offer.

What's New

  • Leafy Greens

    Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso...
    Posted to General (Forum) by gender on 03-03-2015
  • Re: Record or page compression

    Record compression is simple Run-Length Encoding (RLE). This is a high-speed compression and decompression system that simply shrinks 5 or more consecutive bytes with the same value into a compressed representation. It is best for records which have long repeating runs of nulls (0x00) or spaces (0x20). Each record is decompressed as it is accessed,...
    Posted to PSQL v12 (Forum) by BtrieveBill on 03-03-2015
  • Record or page compression

    What are the pros and cons of both? I saw that with record compression about 2 times more records will fit in the Pervasive cache. So I assume that the records are stored compressed in the cache, what's the delay for the server when accessing these records and transfering them to the client?
    Posted to PSQL v12 (Forum) by robebp on 03-03-2015
  • Re: Large string and memo field

    Hi Bill, Yes, I'm using Magic. I remember what you said from Btrieve 6. I'm going to split the tables so that I have only an ID and a Text part. I also have a question about record compression. But that's for another thread.
    Posted to PSQL v12 (Forum) by robebp on 03-03-2015
  • Re: Large string and memo field

    Since "MEMO" is not a valid PSQL data type, can I assume that you are using the Magic Development Environment? If so, then the use of Magic MEMO fields is very different, as it is all handled in code. You will NOT be able to reliably access the MEMO fields from SQL. MEMO fields are physically stored as a 2-byte length field, followed by that...
    Posted to PSQL v12 (Forum) by BtrieveBill on 03-03-2015