Wednesday, August 4, 2010

Find out the benefits of becoming a Pharmaceutical Technician

Join the fast growing field of health care





2009/8/11 Mads Bondo Dydensborg < mb ... @dbc.dk >: I agree it is limited. But, you can actually use it to create bugs, display lists of bugs and a number of other things. I know - that's a bit better than Trac, but not what I was hoping for. I wrote a C# proxy for it, which interesstingly, was usuable outside my own organization: http://www.codeproject.com/KB/vb/BugZillaImporter.aspx That puts bugzilla back down to the same "hey you can always screenscrape" level solution as Trac that I wanted to avoid. Yes, this is a pain. Yes, I've basically given up on the padre plugin now, as I have plenty of things I'd sooner do that write code to screenscrape bugtrackers that haven't managed to crawl into the 21st century ;p Somebody let me know when bugzilla lets you do useful things via a webservice You can always follow the bugs at https://bugzilla.mozilla.org/query.cgi - select Product Bugzilla, component WebService. You may even want to contribute some code/time towards the goal. That's part of the problem - I could do that but it would require anybody who wants to use the code I write that uses the new webservice features to get their bugzilla updated to the release it eventually makes it to, so it would solve my current problem in 18 months, 3 or 4 years - depending on how often the majority of the userbase updates bugzilla. I was looking for something that would give an immediate "wow" factor to the padre IDE, this avenue looks like a dead end until at least one bug tracker manages to provide actual interactive webservices - much as it's tempting to write an extension that does it, it would still not help as most bugzilla users would never have any input on when the server get's updated or any extra bits installed. oh well. A. -- Aaron J Trevena, BSc Hons http://www.aarontrevena.co.uk LAMP System Integration, Development and Consulting - To view or change your list settings, click here: _______________________________________________ dev-apps-bugzilla mailing list dev- ... @lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla Scott Bailey wrote: Tom Lane wrote: Asher Hoskins < ash ... @piceur.co.uk > writes: I can't seem to get to_timestamp() or to_date() to work with quarters , The source code says * We ignore Q when converting to date because it is not * normative. * * We still parse the source string for an integer, but it * isn't stored anywhere in 'out'. That might be a reasonable position, but it seems like it'd be better to throw an error than silently do nothing. Anybody know what Oracle does with this? +1 for throwing error. Oracle 10g throws ORA-01820: format code cannot appear in date input format. Well, I can easily make it do what you expect, and I don't see many error returns in that area of the code, so I just wrote a patch that does what you would expect rather than throw an error. test=> select to_date('2010-1', 'YYYY-Q'); to_date ------------ 2010-01-01 (1 row) test=> select to_date('2010-3', 'YYYY-Q'); to_date ------------ 2010-07-01 (1 row) test=> select to_date('2010-7', 'YYYY-Q'); to_date ------------ 2011-07-04 (1 row) -- Bruce Momjian < bru ... @momjian.us > http://momjian.us EnterpriseDB http://enterprisedb.com PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do Index: src/backend/utils/adt/formatting.c =================================================================== RCS file: /cvsroot/pgsql/src/backend/utils/adt/formatting.c,v retrieving revision 1.168 diff -c -c -r1.168 formatting.c *** src/backend/utils/adt/formatting.c 26 Feb 2010 02:01:08 -0000 1.168 --- src/backend/utils/adt/formatting.c 3 Mar 2010 03:29:05 -0000 *************** *** 2671,2685 **** s += SKIP_THth(n->suffix); break; case DCH_Q: ! ! /* ! * We ignore Q when converting to date because it is not ! * normative. ! * ! * We still parse the source string for an integer, but it ! * isn't stored anywhere in 'out'. ! */ ! from_char_parse_int((int *) NULL, &s, n); s += SKIP_THth(n->suffix); break; case DCH_CC: --- 2671,2678 ---- s += SKIP_THth(n->suffix); break; case DCH_Q: ! from_char_parse_int(&out->mm, &s, n); ! out->mm = (out->mm - 1) * 3 + 1; s += SKIP_THth(n->suffix); break; case DCH_CC: -- Sent via pgsql-hackers mailing list ( pgsq ... @postgresql.org ) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers