myDBR 4.3 - "Self Service"

(6 posts) (3 voices)
  • Started 4 years ago by myDBR Team
  • Latest reply from myDBR Team

Tags:

No tags yet.

  1. myDBR Team, Key Master

    myDBR Team is happy to announce the the availability of myDBR 4.3 release.

    myDBR 4.3 release contains new functionality, fixes and general improvements. The release is recommended for all users.

    Users can now reset their own password if expired / forgotten (feature is off by default). Password reset feature sends user a password reset link mail, so mail settings needs to be configured. Mail settings are moved from a configuration file into the Environmental Settings. Old mail configuration settings can be removed once the new ones are in place.

    New functionality:

    • User can reset own password when using myDBR authentication by requesting a password reset link via mail
    • User can update email address and phone numbers in preferences
    • Improved PHP 5.5 support
    • MySQL socket added as install option
    • Dashboard allows full reports with full functionality
    • Meters and pyramid/cone/funnel charts now support report linking
    • Allow to define own styles in mail
    • Import character conversion possible with 'charset' option
    • Linked reports can be added to html5-data element to be accessed via JavaScript
    • Allow to block Single Sign-On users as admin (local only admins)
    • Conditional linked reports with show_link-parameter
    • Ability to add Cancel-button to dialogs (append '&cancel_button=1' to url)
    • dbr.hidecolumn.summary command added
    • legend.position option added to charts
    • legend.style option added to charts
    • category_sort option added to charts
    • ip_address & user_agent added into statistics
    • no_scroll_to added to embed_object preventing scrolling to embedded element
    • regression_degree option added for trendline's polynomialRegression
    • dbr.colstyle now supports column references when used with charts
    • tooltip chart option supports column references

    Fixes:

    • E_STRICT handling in older PHP
    • Special characters handled better in in-cell editing, linked reports and in parameters
    • Thousand separator in linked reports no longer causes problems
    • Column filter works with multiple tables
    • Improved checkbox parameter handling when no ID's are used
    • Improved UTF-8 support in parameters
    • Clear id's when empty autocomplete is entered
    • Workaround for InfiniDB commenting bug
    • Translation with Bing works again

    General improvements:

    • Mail settings moved into the environmental settings
    • Memory optimizations
    • Dialogs movable in touch devices
    • Dialog positioning now always onscreen
    • Cleaner fonts in SQL Editor when using Firefox
    • adLDAP works with php55
    • Security improvements
    • Improved error handling
    • Export files have now always a name
    • Import supports automatic parameters
    • Tabs can how handle link to report folder (m-parameter)
    • Missing privileges shown in SQL Editor
    • More flexible for integer and float input fields
    • Allows all params to be optional when linked report is called
    • Allow sorting in editable selectlist
    • Commmand change dbr.hidedatacolumn -> dbr.hidecolumn.data (old kept for compatibilty)
    • dbr.calc works with dbr.crosstab.col
    • dbr.colstyle support added to the editable
    • dbr.cellformat support in dbr.editable
    • Crosstab tooltip is now optional (defined in defaults)
    • Improved language detection

    As always, you can update to new version using the myDBR's automatic updater.

    Happy reporting,
    --
    myDBR Team

    Posted 4 years ago #
  2. tyrub, Member

    Hi, this time the update failed bad. I don't have full privilegues on the server so I could not activate stored functions. I clicked on ignore but now I get this error on every report:

    FUNCTION xyz.mydbr_style does not exist

    what went wrong?

    regards
    Daniel

    Posted 4 years ago #
  3. myDBR Team, Key Master

    Assuming your reports use the mydbr_style-function.

    Most likely your user account does not have privileges to create functions (MySQL CREATE FUNCTION requires MySQL SUPER privilege if binary logging is enabled in the server).

    The mydbr_style is created after the installation is otherwise completed.

    The mydbr_style function is not necessarily required, but you can create it if your report code uses it.

    CREATE FUNCTION mydbr_style( inStyle varchar(150) ) RETURNS varchar(400) DETERMINISTIC READS SQL DATA begin declare vRet varchar(400); select definition into vRet from mydbr_styles where name = inStyle; return vRet; end $$
    --
    myDBR Team

    Posted 4 years ago #
  4. ziuras, Member

    Updating database Failed
    Encountered an error during sql-script execution. Fix the error and press retry.

    Type time is not a defined system type.
    create procedure sp_DBR_StatisticsSummary
    .....

    when i run create procedure from Ms sql (2005) manager I got an error:
    Msg 243, Level 16, State 1, Procedure sp_DBR_StatisticsSummary, Line 43
    Type time is not a defined system type.
    (select
    'dbr.rownum' as '#',
    r.name as 'Report',
    s.proc_name as 'StoredProcedure',
    cast(cast(dbo.fn_seconds_to_time(min(datediff( second, s.start_time, s.end_time ))) as time) as varchar(8)) as 'MinTime', ....
    )

    Posted 4 years ago #
  5. myDBR Team, Key Master

    The update has actually been completed. You can turn SETUP_DONE to true in mydbr_config.php.

    The problem occurs after the actual update when the statistics report is added. The report fails as you are running old SQL Server 2005 which does not have 'time' datatype.

    We'll make the script work also again in SQL Server 2005. Sorry for the trouble.

    --
    myDBR Team

    Posted 4 years ago #
  6. myDBR Team, Key Master

    SQL Server 2005 compatible statistics reports have been added. Run the updater to get the latest build and re-run the install script.

    --
    myDBR Team

    Posted 4 years ago #

Reply

You must log in to post.