Closed (fixed)
Project:
Progress
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Mar 2012 at 14:19 UTC
Updated:
27 Sep 2012 at 07:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
gielfeldt commentedHi guenoz
I'm aware of this. I began on a version for postgres for 6.x, but haven't got around to finish it yet. It does work on MySQL though in spite of the reserved word.
I'm not sure when I'll get it fixed for postgres, so for now it's not supported :-(. Sorry.
I'll leave this ticket open for the refactoring task, so that you may follow the progress.
Comment #2
thekevinday commentedI would call this an SQL compliance bug.
The three reserved words are: start, end, and current.
The solution is to not use reserved words.
Problem solved, attached is a patch.
Please review to make sure I did not miss anything.
I will be attempting to fix background_process and ultimate_cron to make sure they are SQL standards compliant as well.
References:
- http://drupal.org/node/141051
Comment #3
gielfeldt commentedCool. Thanks. The reason I haven't looked at this issue yet is because of my tight db coupling from ultimate cron and background process. I was planning on solving this somehow, by avoiding selects directly to the progress table from these two modules.
Comment #4
thekevinday commentedThe only problem I see with this is the API change required.
So, it will work for those who apply all appropriate patches.
But I imagine you'd only be able to make this official by starting a 2.x branch to avoid API breakage.
Comment #5
gielfeldt commentedHere's the Progress patch as mention in #1751176: SQL Compliance, such as with postgres
Comment #6
thekevinday commentedComment #7
gielfeldt commentedCommitted to dev!