Zikula Community

• **unknown user**
  
  

  • Rank: Softmore
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 379

  Posted: Feb 25, 2005 - 09:30 AM

  So in this lovely new module, I have an auto-increment table for the proposals that will be entered. All well and good, except that some of the proposals are going to be re-submitted in the future, because people may be asked for more information. Both proposals need to be available but linked.
  
  If we were doing this by hand, we'd just call them 110 and 110R. However, that breaks down on the auto-increment level.
  
  Any thoughts? The only thing I can think of would be a "resubmitted" table, and just do a couple of queries to get all the proposals. Or something like that. I'm drawing a total blank. Probably a symptom of it being Friday. :)

  • 
  •  
• ctimmer
  
  

  • Rank: Softmore
  • Registered: Feb 07, 2003
  • Last visit: Jun 11, 2008
  • Posts: 225

  Posted: Feb 25, 2005 - 09:51 AM

  I would add a second field called something like base_proposal. In your example above the original proposal would have zero in the base_proposal field and the resubmitted proposal would have 110 in the base_proposal field. No change to the auto-increment logic. This would tie all of the resubmitted proposals to the original.

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6840

  Posted: Feb 25, 2005 - 10:23 AM

  Either that or allow for "resubmit" on the proposal, and use a revison field to store which revision it is.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
•  
•  

Users on-line

• mazdev

This list is based on users active over the last 60 minutes.