Antelope : RAM Operations

[zolting]

Added the RAM Operations table for Antelope.

Operation field (depecrated, replace by action_index + action) is included for retrocompatiblity

[DenisCarriere]

Oh, whenever there's a *_to_string() conversion, I also include the *_code as uint8

• operation_code
• namespace_code
• action_code

[DenisCarriere]

For PRIMARY KEY, I'm not sure if unique_key is actually unique, I believe it represents the unique key of the table row, but it's not actually unique per event, meaning this key could be duplicated within the same transaction

Confirmed, unique_key isn't unique per each new event

SELECT
    unique_key,
    count()
FROM eos.ram_ops
GROUP BY unique_key
ORDER BY count() DESC
LIMIT 10

Query id: 2d665685-646c-41a0-9fee-0473702358b3

┌─unique_key───────────────────────────┬─count()─┐
│ playuplandme:ir1d3fattbmc:t4:        │     136 │
│ playuplandme:ir1d3fattbmc:t4         │     136 │
│ playuplandme:ku33v4yekn1j:t4:        │     102 │
│ playuplandme:ku33v4yekn1j:t4         │     102 │
│ lend.defi:lend.defi:globals:claiming │      42 │
│ playuplandme:voxvaet15huk:t4         │      42 │
│ playuplandme:voxvaet15huk:t4:        │      42 │
│ playuplandme:xgi1rnwwcnff:t4         │      40 │
│ playuplandme:lsobgp3joaaf:t4         │      40 │
│ playuplandme:xgi1rnwwcnff:t4:        │      40 │
└──────────────────────────────────────┴─────────┘

[DenisCarriere]

Updated PRIMARY KEY to:

PRIMARY KEY (tx_hash, action_index, unique_key)
ORDER BY (tx_hash, action_index, unique_key)