# Reblogs

Reblog related operations are not associated with a dedicated transaction, they are stored in the blockchain using `custom_json` transactions (see [TxCustoms](https://docs.hivesql.io/technical-informations/operations/txcustoms)).

Storing the details of a "reblog" operation in a JSON string is pretty annoying because this requires deserializing the content of the JSON string before you can analyze its contents.\
Even if the SQL server has JSON functions to perform such operation, this will slow down queries as the server has to process every row before being able to filter data. Unfortunately, it is not possible to create an index on values contained in the JSON string.

Searching for reblogs is all but efficient, especially when you know that the [TxCustoms](https://docs.hivesql.io/technical-informations/operations/txcustoms) table contains **several million rows**!

Moreover, the format of the JSON string of "reblog" operations has changed over time. This has to be taken into account when parsing the data. Writing an efficient query can quickly become cumbersome.

The table is a non-transactional table that enables one to know who has reblogged which post. It does not store transactions, meaning it does not expose historical data and does not allow to know when an account reblogged a post or removed the reblog.

#### Columns

| Name      | Description                      |
| --------- | -------------------------------- |
| account   | account doing a reblog           |
| author    | author of the reblogged post     |
| permlink  | permlink of the reblogged post   |
| timestamp | when the post has been reblogged |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hivesql.io/technical-informations/state-tables/reblogs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.