NSS MySQL - Patches: patch #1316, Allow for explicit table/where...
You are not allowed to post comments on this tracker with your current authentication level.
patch #1316: Allow for explicit table/where clause for group membership
Submitter: | Invalid User ID <#17263> | ||
Submitted: | Fri 21 Mar 2003 10:26:38 PM UTC | ||
Category: | None | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | gmorin | Open/Closed: | Open |
Mon 24 Mar 2003 11:28:21 PM UTC, comment #2: |
Invalid User ID <#17263> |
Mon 24 Mar 2003 10:22:04 PM UTC, comment #1: Hey,
|
Guillaume Morin <gmorin> |
Fri 21 Mar 2003 10:26:38 PM UTC, original submission:
We're using complex table phrases that already have LEFT JOINs in them, so the auto-join that the group membership code does ends up not making any sense. For this situation, we needed a way to explicitly specify the table and where clauses.
|
Invalid User ID <#17263> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2003-03-24 | gmorin | Assigned to | None | None |
Powered by Savane 3.13-cf05.
Corresponding source code
Oh! No, those shouldn't be mandatory. I was just following the format of the table. I honestly didn't look up what it meant. :)
If it's "0", will it still get initialized to an empty string if the option is missing? The code that tests for that option depends on it.