Year Change does not create correct rate table [manually SOLVED]

Post here if you think you have found a bug in hoteldruid or error in its documentation.

Moderator: marco

Post Reply
nethead
Posts: 18
Joined: Thu Jan 06, 2011 7:48 am

Year Change does not create correct rate table [manually SOLVED]

Post by nethead »

Hello,

i did just do the year change creating the 2021 sql tables and php scripts. Unluckily only one of my rates did made it to 2021? Please see attached images. Any ideas why this happens and how to fix it?

My 2020 rate tables has about 16 rates, my 2021 rate table only 1?! I did backup the database before doing the year change, like always. And tried twice using the default of the daily rates to bring over to 2021.

I am using the latest version, 3.01

cheers,

Arnd
Last edited by nethead on Tue Aug 22, 2023 1:20 pm, edited 1 time in total.
nethead
Posts: 18
Joined: Thu Jan 06, 2011 7:48 am

Re: Year Change does not create correct rate table

Post by nethead »

CORRECTION: There had been one table copy missing. This are the complete instructions to manually copy your rate tables via sql and texteditor.

I did check the sql table and the rates did not get copied from periodi2020 into periodi2021. This did fix it:

Note: Use your current year as the postfix of the tables, i.e. regoleXXXX and periodiXXXX where XXXX is your current year. Use periodiYYYY and periodiYYYY from the year you want to copy your rate table from. I am copying from 2019 to 2023 (current year for me now)

Code: Select all

drop table periodi2023;
drop table regole2023;

CREATE TABLE  regole2023 LIKE regole2019;
CREATE TABLE  periodi2023 LIKE periodi2019;


INSERT regole2023
SELECT * FROM regole2019;
Now for periodi2023 we cant just copy from the older table but must export it and then replace the old year with the current year, in my case, again, old year is 2019, current year is 2023;

You must export the table periodi2019 to a text file, then replace all occurances of "2019" with "2023". After this you import this data into periodi2023. Done

cheers,
Last edited by nethead on Tue Aug 22, 2023 1:19 pm, edited 2 times in total.
marco
Posts: 1332
Joined: Tue Jul 05, 2005 6:00 pm
Location: Roma, Italia

Re: Year Change does not create correct rate table

Post by marco »

Hello Arnd,
maybe you hit a memory limit or time limit? You can check the logs if there was an error. Hoteldruid tries to expand the execution time limit if allowed by configuration.

Regards,
Marco
Problems installing, configuring, upgrading?
Try the easiest way to use HotelDruid:
https://www.digitaldruid.net/hosted/index.php
nethead
Posts: 18
Joined: Thu Jan 06, 2011 7:48 am

Re: Year Change does not create correct rate table

Post by nethead »

Hi,

i did just correctly migrate the extra costs using this:

Code: Select all

drop table ntariffe2023;

CREATE TABLE  ntariffe2023  LIKE ntariffe2019;

INSERT ntariffe2023
SELECT * FROM  ntariffe2019;
Instead of "ntariffe2019" use the year where you know your extra costs had been correct. Instead of "ntariffe2023" you probably want to use your current year. I.e. "ntariffe2025".

Note: In case the definition of the "ntariffexxxx" table will be changed this wont work anymore...

cheers...
Post Reply