Tickets :: Comment on [#6295] Ansel flat shares with hierarchies

* Your Email Address
* Spam protection	Enter the letters below: . ,._.. .. .. , \./ \| \|\ \|\|\/\| \./ \| _\|_\| \\|\| \| \|
Comment	>> I haven't looked at your patch yet, but I will say that I'd prefer to > >> keep the shares and galleries table separate. IMO it makes for a > >> cleaner implementation and keeps the share implementation/driver > >> decoupled from the gallery objects. But I'm definitely open to > >> other's thoughts to convince me otherwise. > > > > By combining we can remove 3 columns and have one join less. It will > make data more compact and much faster and memory friendly which is > always a strong point for large systems. > > > > But your wish is not a problem for me, beside data being proccessed. > Moving the storage mechanism on driver bases, will allow me to have > my own performance driver and combined tables. When someone can still > use the classic DT implementation or this share driver. > > > > So the next step will be defenitly be to separate the storega classes > with driver abstraction. Making my work easier possible to have > different testing drivers without affecting Ansel core. > >
Attachment
Watch this ticket