You are viewing limited content. For full access, please sign in.

Question

Question

boolean fields (i.e. checkbox fields)

Workflow Version 9 Ideas
Updated July 23, 2024
asked on March 13, 2014

As far as I can tell Laserfiche does not have a Boolean field type.  I would find it useful for Workflows mostly for checking, say, if such-and-such a page or form is attached. 

 

So, this is possibly a feature request.  Any plans to add Boolean field type in the future?

 

1 0

Answer

APPROVED ANSWER
replied on March 13, 2014

I've typically seen this handled with a List field that has 'Yes' or 'No' as values.

1 0

Replies

replied on March 17, 2014

While its slightly more efficient, its not as efficient as you would think. A bit field in MSSQL actually uses one byte if its the only bit column in your table. http://msdn.microsoft.com/en-us/library/ms177603.aspx

 

The list field offers much greater versatility because if you ever decide you want to add a third choice, like "Needs Approval' or 'N/A' etc. then you'd have to deal with the data conversion back to the string.

replied on July 23, 2024

While its slightly more efficient, its not as efficient as you would think. A bit field in MSSQL actually uses one byte if its the only bit column in your table.

 

Slightly misleading. If you had 8 values to store in "bit" data type columns, it would STILL only use 1 byte.  For 9-16, it moves to 2 bytes, and so on in increments of 8s obviously (8 bits in a byte).  So... the measure of efficiency or lack thereof is directly related to the number of these types of volume you'd need to store in a given row. 

Yes... I took time to respond to a 10 year old post with this.  ;)

0 0
replied on March 13, 2014

Yes, that's how I have been doing it, but I was just thinking booleans would be more efficient, database-wise.  A yes/no list field takes up 3 bytes, I would think - whereas a boolean field takes up 1 bit.  I'm not a database guy, but I would think it would be about 20x more efficient.

0 1
replied on March 17, 2014

While its slightly more efficient, its not as efficient as you would think. A bit field in MSSQL actually uses one byte if its the only bit column in your table. http://msdn.microsoft.com/en-us/library/ms177603.aspx

 

The list field offers much greater versatility because if you ever decide you want to add a third choice, like "Needs Approval' or 'N/A' etc. then you'd have to deal with the data conversion back to the string.

0 0
replied on March 17, 2014

Ed,

Ahh, I understand, that does make sense.  Also, there's no denying a List field is more versatile for the exact reason you mention.  Thanks for the response.

 

John

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...