Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v6r11] Some fixes for WMS #2093

Merged
merged 22 commits into from
Oct 1, 2014
Merged

Conversation

fstagni
Copy link
Contributor

@fstagni fstagni commented Sep 25, 2014

There are also changes to comply to the Data Model https://docs.python.org/2/reference/datamodel.html#object.__nonzero__ for the RMS and DMS, that was causing a real bug (RequestName was wrongly set in FailoverRequest.py)

Some (old, broken) test files for WMS DBs have been removed and are now in TestDIRAC


##############################################################################
types_getSiteMaskLogging = [ list(StringTypes)+[ListType] ]
def export_getSiteMaskLogging(self,sites):
types_getSiteMaskLogging = [ [StringTypes, ListType] ]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bug, the previous was correct, StringTypes is a tuple

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, I correct it now

@atsareg
Copy link
Contributor

atsareg commented Sep 27, 2014

Forget my comment about the nonzero. I overlooked your mail.

atsareg pushed a commit that referenced this pull request Oct 1, 2014
@atsareg atsareg merged commit 5e0f8d5 into DIRACGrid:rel-v6r11 Oct 1, 2014
@fstagni fstagni deleted the fixesWMSv6r11 branch January 29, 2015 16:17
) ENGINE = InnoDB;
DROP TABLE IF EXISTS `Jobs`;
CREATE TABLE `Jobs` (
`JobID` INT(11) UNSIGNED NOT NULL DEFAULT 0,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fstagni Can you confirm that this AUTO_INCREMENT was dropped on purpose

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it was dropped on purpose: the "main" table is in fact JobJDLs (where AUTO_INCREMENT on JobID is maintained), not Jobs, where we have that FOREIGN KEY (JobID) REFERENCES JobJDLs(JobID),

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fast response and the explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants