pricing tables?

[sandys]

hi,
am not sure if you consider this in the ambit of a ledger, but generally it has been ULTRA useful.

does this (or will this) support pricing tables ?

drawing from SAP examples,
CKMLCR : Ledger Period totals records value
CKMLPR : Ledger Prices
CKMLPRKEPH : Ledger Cost component split
MLCRP : Ledger Price Changes (currencies)

[pgr0ss]

I don't understand. Can you link to some docs or usage examples for pricing tables? What functionality does it add?

[sandys]

so a particular ledger transaction can be associated with a certain price. in your case it will be metadata.
for e.g. buy apples for 2$ per pound with a 30% discount applied for more than 5 pounds and a cashback of 50cents.
now one thing that you can do is store this entire pricing "rule" in the metadata field. which will result in duplication.

the other way is to make a separate table of these. but then we have to join a jsonb key to this table. is this what you have been envisioning ?
or have you always envisioned copying over all data and store it in metadata ?

[pgr0ss]

I think in this case I would model it in separate tables as I think it's distinct enough from what pgledger is doing. And then I would probably store the foreign key in metadata, or you could change the schema in your app's version of pgledger and make it a top level column.

[sandys]

So the intent for me posting about this is that - sure, the data is maintained separately. But it would be good for performance if the ledger allowed for a column that is a "nullable external foreign key". The metadata jsonb column is fine...but performance is not so good.

…

On Fri, 5 Dec, 2025, 11:57 Paul Gross, ***@***.***> wrote: *pgr0ss* left a comment (pgr0ss/pgledger#115) <#115 (comment)> I think in this case I would model it in separate tables as I think it's distinct enough from what pgledger is doing. And then I would probably store the foreign key in metadata, or you could change the schema in your app's version of pgledger and make it a top level column. — Reply to this email directly, view it on GitHub <#115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAASYU7M7KGFBS7CL2AUO3D4AEQTXAVCNFSM6AAAAACM7XQ7XCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJVGQ4DMOJZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pgr0ss]

You can always add the column to suit your needs. Since pgledger is just SQL, when you copy it into your project, feel free to change it as you see fit.