| Author |
Message |
|
|
Hi,
since I'm working with the OLAP reporting in Wabit I keep findind possible improvements:
- Add slicer to OLAP GUI: Other tools allow you to set a filter or slicer. It creates the MDX part "where"...
- Show when MDX query execution is finished. Right now you can't really see if a query run or not.
- Keep executed MDX query. Right now you can run a MDX query but it doesn't save it once you switch to the report or anywhere else.
Where can I set the memory for Mondrian? What is the default value for it?
I'll post more comments here by time.
Benjamin
|
 |
|
|
It is strange, Power*Architect decided to change it's behaviour. When I click on ok now, it doesn't do any changes and the value of the field "Create in" switches back to "(Target database)"
I have the build from June 19th
|
 |
|
|
Hi,
i reported the same bug earlier, it should be fixed in the latest nightly build. See this post for more details: http://www.sqlpower.ca/forum/posts/list/2363.page
Benjamin
|
 |
|
|
Hi,
it would be very helpful to support the attribute "LevelType" in the frontend to be able to create time dimensions. Right now you can only set the dimension type. Mondrian expects level types inside time dimensions.
Benjamin
|
 |
|
|
Hi,
thanks for fixing it. It is still alive in another part of Power Architect (newest version from Hudson today)
How to find it:
- Create a new project
- Add Connection
- Edit connection
- Save without changes
Benjamin
|
 |
|
|
Hi,
the columns a report is grouped by should only show up in the summary by default. This would improve the design of a report a lot since you save a lot of space.
Benjamin
|
 |
|
|
I don't think there is anything wrong with it, I just try to avoid it in Postgres if I have to use Kettle in the same project.
Benjamin
|
 |
|
|
I just wanted to bring up the Postgres type TEXT again, I had issues with it yesterday. I also saw a model that was created based on a Postgres database and it converted TEXT to a huge VARCHAR. I don't have any time to reproduce it though.
About the Postgres TYPE BOOLEAN: Also Kettle has issues with it, and in the forum people recommended changing into a integer instead.
Benjamin
|
 |
|
|
Hi,
a very helpful feature for Wabit would be the ability to define defaults settings for table columns. These settings could include:
- Business name (even multilingual)
- Formatting (Number, Currency)
- Alignment
- Thresholds
- Column width
The reason behind is that dealing with many reports against the same table or tables with similar content you spend lots of time with formatting every single report instead of defining it once and use the same format in all reports.
In case a change is needed (eg. different alignment) I have to open every single report and change it. With the new feature there would be one central location to change it only once for all reports.
Have a look at Pentaho Metadata, it does the same and even more. Maybe you can even use it (it's GPL).
Benjamin
|
 |
|
|
Hi,
it would be great if I could use templates in Wabit so I can reuse the same footer, header, images, fonts etc. Especially when using Wabit for larger projects where you have to create 20+ reports this will save you lots of time.
Benjamin
|
 |
|
|
Working with a new Model made me think of another improvements, related to regions:
- Having regions you could print or hide selected regions to get a better overview.
- For DW it could be helpful to have have attributes for tables to select if it's a fact table, dimension table, code table ..... Together with a Default Color Schema in the Project Properties the color of a table could be automaticallly set depending of the kind of table (all fact tables green, dimensions blue,....). This would help a user to understand a model a lot faster.
Benjamin
|
 |
|
|
I think it does make sense to be able to select a database where you can create your model in. You could move the dialog to select the database to the screen where the SQL Script can be executed.
I can't think of a better name than target database, but maybe you could just write "SQL Script will be executed in <Database>" if you don't want to use the term"Target". Is there any other dialog where term target is used?
Benjamin
|
 |
|
|
Hi,
have you thought about creating a Kettle plugin for DQGuru? This could help to do data cleansing during ETL process. Users could set up the processes in DQGuru and then call them out of Kettle.
Benjamin
|
 |
|
|
How to recreate the bug:
- Create a database connection
- Start the Forward Engineer SQL Script
- Select your target Database
- Click on Properties
- Don't do any changes and click on Ok
- You'll get a message "A connection with the name <ConnectionName> already exists.
Benjamin
|
 |
|
|
As a user I would like to run a report in the background and get a notice
(maybe popup) once the report is ready. This way I can still use Wabit
while running a bigger report (query runs a couple minutes) instead of
waiting for Wabit.
Filed at http://code.google.com/p/wabit/issues/detail?id=21
|
 |
|
|