Recorder: how "weather" entities are stored in DB?

Configuration
1

Weather entities from integrations which I am using (Metno, Gismeteo, OpenWeatherMap) have forecast data.
Can anyone tell me how these entities are stored in DB?
Is there any “optimization”?

I believed that storing forecast data needs more space - so I simply excluded “weather” domain from Recorder and use template sensors for curr. values like temperature etc (which are included in Recorder).

2

All entities are stored the same in the database. They have 2 separate tables, one for the state, one for the attributes. Yes it will take up more space because it’s a larger set of attributes.

3

Thanks for the reply!
Will keep excluding weather entities from Recorder then.

4

It might be worth noting here: Interestingly, weather forecasts are not real attributes, but provided by a separate API. So, those forecasts are not stored in the database 🤷 (see Weather Entity | Home Assistant Developer Docs). I double-checked in my database and they are not in the state_attributes table.