Sorry yes, I meant Char(). Bob S
> On Mar 2, 2015, at 20:00 , Dr. Hawkins <doch...@gmail.com> wrote: > > On Mon, Mar 2, 2015 at 9:25 AM, Bob Sneidar <bobsnei...@iotecdigital.com> > wrote: > >> To optimize connections and transfer of data, one of the things you can do >> is use VarChar() instead of TEXT whenever possible. A very knowledgable web >> designer explained to me that TEXT types pad the storage values to fill the >> defined storage size for that column, whereas VarChar only stores as much >> data as is in the column for that record. >> > > But TEXT has undefined object size. According to postgres, there is not an > efficiency difference between VARCHAR an TEXT. > > Perhaps he/you meant CHAR(), rather than TEXT? > > >> Another thing you can do is avoid querying for BLOB types until you >> actually need the data. Thirdly, I suspect as others have said, that using >> transactional querying, and combining all your SQL statements into one >> using the semi-colon delimiter is probably going to save some time overall. >> > > I don't know about BLOB, but isn't it also varying size? > > > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
