Hi Jason, The property values and objects in general in AGE are encoded as JSON/JSONB, which are basically strings in the end. By doing it this way, it allows objects (properties are objects) to be more flexible with what they contain. But yes, there are always tradeoffs and that means there is bound to be some performance lost due to this choice.
However, this format is a native PostgreSQL format so, it benefits by some of their internal optimizations and continued development. Additionally, we are always looking to optimize AGE where we find performance issues. Hope that is helpful. john On Sun, Mar 13, 2022 at 3:48 AM Jason Filby <[email protected]> wrote: > Hi, > > I'm looking at using Apache AGE for a project. My one concern is that all > property values appear to be strings, is that correct? Isn't there a loss > of performance for querying based on properties that would have int64 > values, but are converted to strings? > > Thanks > Jason > >
