Make your own free website on Tripod.com

InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: InstantDB: Re: Bug in InstantDB !? A lot of null bytes in DB Tables


I've had to give this advice to others as well, having figured it out the hard 
way ...

The reason the question comes up is that VARCHAR is typically just that: 
VARiable-length CHARacter.  Every other db I've dealt with allocates variable 
length storage for VARCHAR types: any chance of InstantDB getting a bit more 
standard in this regard in the future?

Regards,
Liam Graham

Quoting Thom Nelson <thom@lutris.com>:

> Hi Elmar,
> 
> VARCHAR allocates fixed space for the data; in order to get true
> variable length allocation, use the TEXT datatype instead.
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.