Guilty was this one:

"sample3_post_metadata"."description" AS "sample3_post_metadata_description" 

Of course you can shorten also table name. Wish me go that way?

shortening column names isnt a fix there. Do you expect users would be pleasured to do so too? We need some good fix. I don't understand why oracle support on aliases length is so limited.

May be we can generate aliases somehow shorter?

ahhh Im not sure... Do you have any ideas?

Hmm just a question. Why you need to give them aliases at all?

ahhh thats a long story.... we need aliases to map data correctly to entities. You need to learn code of QueryBuilder and RawSqlResultsToEntityTransformer to understand why they are needed.

Probably we have only one way of fixing this - shorten them. But im not sure what is effective way of doing this. Maybe cut half of table name and column name in query builder? Not really sure. Is there any way we can increase alias length in oracle via orm?

Also, if you are planning to work on QB I recommend to switch to this branch, because there are latest changes of everything

How about giving them numbers? Like Alias1, Alias2, .... AliasN

we can try numbers, however it will make things much much more complicated. And its already quite complicated

@gintsgints we are planning to finish complete oracle support in 0.2.0. @AlexMesser already fixed most of issues oracle has on his own branch. Soon all those changes will be landed in next and final 0.2.0 will be released next month. Thank you very much for your contribution.