tmccormi/openemr — comment on commit 050ec3e0c171ce6984a78bd606addef9354926d0
File:  line 0
By tmccormi:

I disagree, the documentation since version 3.2 says to use colon
separators. Therefore doing it any other way would require data
conversion or coding to handle both scenarios. I'm going to leave it
as colon's as planned, documented and already coded.

If I had time I would modify the code to have 4 separate fields in the
tables and in data entry. But that also requires a data conversion on
upgrade. Think of it a a future enhancement that's a better solution
that spaces.
--Tony

On Sat, Dec 3, 2011 at 3:40 PM, Brady Miller

wrote:
> Also agree that using a space seems to make more sense from both a "user experience" and from a "simplify coding" perspectives.
> -brady
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/tmccormi/openemr/commit/050ec3e0c171ce6984a78bd606addef9354926d0#commitcomment-766621
>