# References to Views as a way to emulate Embedded Db's in Notion

**URL:** <https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247>\
**Category:** Ideas & Features\
**Created:** [December 16, 2020, 7:35pm UTC](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247 "2020-12-16T19:35:40Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [April 27, 2021, 8:45pm UTC](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247/13 "2021-04-27T20:45:54Z")

</div>

I hate to say it, but in another example of disorganization here in Discourse, I realized that what we are talking about a bit is already discussed here:

> [@CHANGELOG: March 31 / Insert Videos into Docs, Frames, Better History, many improvements & fixes](https://community.fibery.io/t/changelog-march-31-insert-videos-into-docs-frames-better-history-many-improvements-fixes/1503/7):
>
> Audit Log for schema changes is almost ready, it does include all changes in Types (new fields, etc), but it does not track Views creation/deletion. Hope it will be released next week. Here is the intermediate result

The history of the Type changes looks like it’s planned. However, I’d like to be able to see that right on a Type, so I can see - on the level of the Type - all the changes that have been done. @Chr1sG when you say:

I have noticed that the entity activity history includes entries relating to changes to the type (as well as changes to the entity content of course).

Could you point out where you can see in the existing Activity Log changes to the actual Type? For example, if you add something to a dropdown?

Ultimately I still feel a big need to simply be able to go to a View, Type, or even App, and look at its changes right on that level. And also comment about what you are doing. In a sense you can do this in Notion or Coda, because they embed views, and Types for that matter via individual tables, within pages that you can comment on. Fibery’s fundamental structure is better in that it distinguishes among these items and makes them distinct, but until we can do basic things around ALL the items in Fibery (docs and Whiteboards included), like reference, comment, have history, etc. we are not really where we need to be, I think.

Thanks again!

---

_[View the full topic](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247)._