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

Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes

Subject: Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
From: Chris Travers <..hidden..>
Date: Sun, 30 Dec 2012 02:57:13 -0800

Actually it occurs to me we could use text fields and supply a script to convert these to JSON if the db is 9.2. This would allow us to support 9.1 and higher without having to postpone this feature.

The danger of course would be that if third parties are writing to this field they MUST write JSON or else you have a possibility of headaches on upgrade......

Follow-Ups:
- Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
  - From: Chris Travers

References:
- Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
  - From: Chris Travers
- Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
  - From: John Locke
- Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
  - From: Chris Travers

Prev by Date: Re: Online translator is available for LSMB - Pleasejoin
Next by Date: Proposal to formalize end-of-life
Previous by thread: Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
Next by thread: Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes
Index(es):
- Date
- Thread