Search found 86 matches
- Tue Aug 28, 2018 5:26 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Definitely looks MUCH better. Thank you for sticking with me.
- Tue Aug 28, 2018 5:22 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Ugh! Sorry. Forgot to select my database.
- Tue Aug 28, 2018 5:13 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
I'm getting:
ERROR: relation "pay_period" does not exist
LINE 6: FROM pay_period AS pp
ERROR: relation "pay_period" does not exist
LINE 6: FROM pay_period AS pp
- Mon Aug 27, 2018 11:16 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Checking the old mysql database and the times are EST5EDT. Not sure why I thought it was different. It appears like the export from mysql for postgresql changed all the times to UTC (for pay_periods, not timesheets). Is this possible?
- Mon Aug 27, 2018 10:25 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Ok, so I made a mistake. Any new pay periods are created in the specified system timezone. All the old ones are GMT. I suppose I could fix this with the right SQL, but I'm wondering when this was suppose to be converted.
- Mon Aug 27, 2018 9:55 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Of course, the audit messages would be correct. Not sure what I was thinking there. But what was the point of the other pic? This crazy problem is keeping me from upgrading.
- Fri Aug 24, 2018 10:09 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
I went through exporting the data from mysql and importing to postgres into version 11.0.2 just to see if somehow I missed anything. But the results were the same. The dates and times on the pay periods are correct in the mysql version of 11.0.2 but not in the postgres version. Upgrading to 11.2.5 d...
- Fri Aug 24, 2018 9:55 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Included pay period screenshot and one for the audit of the first pay period.
- Fri Aug 24, 2018 6:33 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
I am TRULY sorry for all these posts. Really I am. But...
On the postgres install, even though the times are four hours in the future (GMT), if I open the pay period and check the Audit entry, it is correct! The times are in EST5EDT.
On the postgres install, even though the times are four hours in the future (GMT), if I open the pay period and check the Audit entry, it is correct! The times are in EST5EDT.
- Fri Aug 24, 2018 6:26 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
I created a new pay period and even though it is GMT in the database, it displays correctly in TT. Why? I checked the start and end times in the database for the new record and a previous one and there is no difference (well, except the date). Both are GMT. So what makes the old record display wrong...
- Fri Aug 24, 2018 5:48 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
The original install is at 10.6.1, if I haven't said that already.
- Fri Aug 24, 2018 5:46 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Further, on my original mysql install, if I change my account preference's timezone, ALL of the pay period times update to the new timezone setting. This is NOT the case with the new install.
- Fri Aug 24, 2018 4:54 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
I just checked our original db, and these dates and times are in fact stored as GMT. So this is not a problem with storage, this is a problem with the display. For some reason they are not being changed to EST. I checked the postgres records and they are also in GMT and after comparing some of the r...
- Fri Aug 24, 2018 4:43 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
Are you telling me that the dates and times are NOT stored in the db as GMT and then converted for display?
The punch times are all correct. This appears to be the only place this is happening.
I did step #4 exactly (I cut and pasted, changing only the un, pw and db name).
The punch times are all correct. This appears to be the only place this is happening.
I did step #4 exactly (I cut and pasted, changing only the un, pw and db name).
- Thu Aug 23, 2018 8:57 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
No matter what I set the timezone to, under the advanced tab, nothing changes. The dates are still GMT.
- Thu Aug 23, 2018 8:44 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
They are set to EST5EDT.
For the record, these were all correct before doing the conversion from MySQL to postgres.
For the record, these were all correct before doing the conversion from MySQL to postgres.
- Thu Aug 23, 2018 6:02 am
- Forum: Help
- Topic: Another daylight saving issue
- Replies: 25
- Views: 13591
Re: Another daylight saving issue
I upgraded our postgres install to 11.2.5 from 11.0.2. But in both the timezone was GMT for all of our pay periods. I set the system_timezone = EST5EDT in the conf file and have confirmed that this is being picked up by the TTLDate class. My system time is set to EST as well, but if I don't set syst...
- Wed Aug 22, 2018 11:07 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
I deleted the 11.0.2 I had and copied it back over from the original zip (I've done this multiple times already) and ran the installer again. This time it worked. No clue as to why.
- Wed Aug 22, 2018 10:59 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
What? Wait...no....that log is from a fresh install of 11.0.2 of the postgres version of TT. It is brand new.
- Wed Aug 22, 2018 9:42 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
Set debug to 10 and attached the output.
- Wed Aug 22, 2018 8:28 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
Somehow I missed step 2. Not sure how. But I've done this so many times over the past month I'm bound to miss something I guess I followed everything very closely this time. When I try to install the 11.0.2 version of TimeTrex on postgres the installer gets through building the db and then it asks f...
- Tue Aug 21, 2018 10:36 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
But then the import to postgres of the converted data fails because of the user_tax table. So it looks like it needs to be deleted after, and only after the upgrade of the mysql version to 11.0.2. But after all that I fail with psql:timetrex_mysql.sql:156327: ERROR: date/time field value out of rang...
- Tue Aug 21, 2018 4:50 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
Looks like user_tax is indeed needed:
DBError::__construct(): Code: DBError(1146) Message: mysqli error: [1146: Table 'timetrex.user_tax' doesn't exist] in adodb_throw...
DBError::__construct(): Code: DBError(1146) Message: mysqli error: [1146: Table 'timetrex.user_tax' doesn't exist] in adodb_throw...
- Thu Aug 09, 2018 7:53 am
- Forum: Installation Help
- Topic: RDS
- Replies: 0
- Views: 20901
RDS
Has anyone tried to install timetrex using postgres or Aurora on Amazon's RDS?
- Mon Jul 30, 2018 9:38 am
- Forum: Installation Help
- Topic: report_schedule does not exist
- Replies: 23
- Views: 15631
Re: report_schedule does not exist
I did do #4 correctly. It still didn't work. So, I started completely from scratch, following each step EXACTLY as written. Once again, I got: psql:timetrex_mysql.sql:90: ERROR: relation "report_schedule" does not exist. I listed all the tables in the postgres db and there is no report_sch...