Re: Empty [] using objects.all() on legacy database

2009-06-23 Thread Karen Tracey
On Tue, Jun 23, 2009 at 12:04 PM, Greg Corey wrote: > Ok. I will work on opening a ticket based on your recommendation, though I > will not have your depth of analysis on the problem. Mind if I quote your > most recent explanation if needed? > Sure, but it's probably not necessary, though you co

Re: Empty [] using objects.all() on legacy database

2009-06-23 Thread Greg Corey
Ok. I will work on opening a ticket based on your recommendation, though I will not have your depth of analysis on the problem. Mind if I quote your most recent explanation if needed? Greg On Tue, Jun 23, 2009 at 8:41 AM, Karen Tracey wrote: > On Mon, Jun 22, 2009 at 2:19 PM, Erik Vorhes wrote

Re: Empty [] using objects.all() on legacy database

2009-06-23 Thread Karen Tracey
On Mon, Jun 22, 2009 at 2:19 PM, Erik Vorhes wrote: > > On Mon, Jun 22, 2009 at 12:52 PM, Greg Corey wrote: > > Karen, the double % ( i.e. 'discount%%') worked. Is this a big enough bug > > that it should be reported? I'm not sure what is a bug and what is just > my > > ignorance. Thank you sooo

Re: Empty [] using objects.all() on legacy database

2009-06-22 Thread Greg Corey
I figured it wasn't a bug and I just had to do the right escape sequence, but Karen mentioned that it might be a bug. Guess not. Hope this helps someone else in the future. Greg On Mon, Jun 22, 2009 at 12:19 PM, Erik Vorhes wrote: > > On Mon, Jun 22, 2009 at 12:52 PM, Greg Corey wrote: > > Kare

Re: Empty [] using objects.all() on legacy database

2009-06-22 Thread Erik Vorhes
On Mon, Jun 22, 2009 at 12:52 PM, Greg Corey wrote: > Karen, the double % ( i.e. 'discount%%') worked. Is this a big enough bug > that it should be reported? I'm not sure what is a bug and what is just my > ignorance. Thank you sooo much for the help. The first % escapes the second % sign, and th

Re: Empty [] using objects.all() on legacy database

2009-06-22 Thread Greg Corey
Karen, the double % ( i.e. 'discount%%') worked. Is this a big enough bug that it should be reported? I'm not sure what is a bug and what is just my ignorance. Thank you sooo much for the help. Greg On Fri, Jun 19, 2009 at 8:09 PM, Greg Corey wrote: > I will try that tomorrow and let you know.

Re: Empty [] using objects.all() on legacy database

2009-06-19 Thread Greg Corey
I will try that tomorrow and let you know. The DB is an old Microsoft Access database that was then migrated to MySQL. It was designed by a definite novice so it has quirks, but it still pumps along. It is a DB of testing results for our small laboratory. Greg On Fri, Jun 19, 2009 at 8:00 PM, Ka

Re: Empty [] using objects.all() on legacy database

2009-06-19 Thread Karen Tracey
On Fri, Jun 19, 2009 at 4:41 PM, geraldcor wrote: > > Ok, so I feel a bit silly, but it was because I had a column name in > my db called Discount% and I am assuming the % is screwing it up. > > Now the question becomes how do I escape the % or do I have to rename > my db column (please god not t

Re: Empty [] using objects.all() on legacy database

2009-06-19 Thread geraldcor
Ok, so I feel a bit silly, but it was because I had a column name in my db called Discount% and I am assuming the % is screwing it up. Now the question becomes how do I escape the % or do I have to rename my db column (please god not the latter as that would entail a whole mess of rewriting stuff

Empty [] using objects.all() on legacy database

2009-06-18 Thread geraldcor
Hello all, I am trying to work with a legacy database and I ran inspectdb and have a model with the 2 tables that I want to use. The first table, the main table is not working at all. The second table which is related via a foreign key seems to be working just fine. Here are the symptoms: In the