Closed GoogleCodeExporter closed 9 years ago
Are you sure you use Alfresco in a correct manner? It si a document management
system right, not a replacement for a database system :-)
I agree on not giving a nice meaningful exception...
Having said that, this is foreseen behaviour. Look at
https://code.google.com/p/alfresco-business-reporting/wiki/AdvancedInstallation#
Exclude_properties_from_appearing_in_the_reporting_database you can either
exclude columns from the reporting tables, or tweak the size of individual
columns. Each Alfresco text field claims a VARCHAR(700). You can adjust this on
the level of an individual property name.
Then again... Did you model this number of properties against a single Alfresco
type?? Please also consider splitting your business objects over multiple
tables. Either on TYPE or on having a particular aspect (or not). This way you
limit the exotic number of properties/columns in a single table.
Remind that the setup as I ship it is a default one, working for all initial
Alfresco installs. For this number of properties/columns it does not make sense
to maintain a table like 'folders' or 'documents'. Please create meaningful
tables for business objects that define your domain. That is what the tool is
made for!
Please let me know if this allows you to continue working... I will not fix the
error message in the older versions. I will consider it in the current version,
although I am not sure about the impact. (I will create a new ticket for this
particular issue then...)
Original comment by tjarda.p...@incentro.com
on 13 Nov 2013 at 1:06
Hello Tjarda:
First of all thanks for such a fast and diligent answer.
The Alfresco where I'm trying is a development Alfresco and I have a mix of
models from different tests and developments, that's why I have such a lot of
models. I'm aware that Alfresco is not the replacemente for a database, in fact
quite often I have to explain this to customers who pretend to use it like this.
But IMHO in quite customized installations having over a dozen different types
or aspects with 4 to 6 metadata fields doesn't seem such a strange scenario.
But this can probably be easily handled with the configuration options you
pointed in the link, I wasn't aware of this information.
By the way, thak you very much for all the hard work behind this project. I'm
still in early testing it but I find the approach of taking data to a "normal"
precalculation database really useful.
Original comment by igor...@gmail.com
on 13 Nov 2013 at 2:08
Original issue reported on code.google.com by
igor...@gmail.com
on 13 Nov 2013 at 12:48Attachments: