well for now i think i'll do direct sql since i know that and i need to wrap this up today.
Was my description of how the tables all fit together correct? Ian Noah Kantrowitz wrote: > I would highly recommend using XML-RPC to do this, not direct SQL. > > --Noah > > On Oct 5, 2006, at 10:45 AM, Ian wrote: > > > > > Hi all, > > > > brand new to trac and brand new to sqlite as well. I have python > > experience and postgres experiece though. > > > > I'm working on a small project where we want to have our own webpage > > which will submit and create a trac ticket. > > > > I think I see how to update the tables using pysqlite. But is there > > any > > sort of db diagram or map explaining all the tables and fields? > > > > Some of the fields on our form match up to fields in the ticket table, > > some do not. I assume for the fields that do not match up, i would use > > the ticket_custom table. ticket_custom.ticket would be the ticket # > > and > > name and value would be the name of the field and the value for that > > field. is that correct? > > > > What about attachments? I see the attachments table but i'm not sure > > how it all works. What is the type and ipnr field for? and how do you > > associate the attachment with a ticket? > > > > if someone could answer that, or point me to the docs that would > > answer > > that, i'd greatly appreciate it. > > > > thanks > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
