Paul McNett wrote: > Uwe Grauer wrote: >> Paul McNett wrote: >>> Okay, we are in slightly better shape with the firebird unit tests, as >>> they run but some of them fail. Here's what I'm seeing: >>> >>> [EMAIL PROTECTED]:~/projects/dabo/dabo/db/test$ python test_dCursorMixin.py >>> EF.F...F.F...E...E.................................... >>> ====================================================================== >> Sorry for answering late on this. >> I didn't understand your attempt to handle this in dabo, >> so i didn't do anything about it. >> >> I already tried to explain what the problem is: >> >> If you do create a table with "create table atable ( aField INT )" >> aField is not case sensitive. >> If you do it with "create table "aTable" ( "aField" INT )" aTable and >> aField are case sensitive. > > Uwe, are you saying that we created the tables with quoted names, and we > shouldn't have, or are you saying that we created the tables without > quoted names and should have, or something else entirely?
First i thought that there was no need to do firebird-DDL with the use of quoted table- and fieldnames , but once there was a request to support table- and fieldnames with spaces we should (should we?). In fact most people don't use quoted names in firebird because it is a hassle most of the time. People use different tools to analyze or manage metedata, so the normal advice from the firebird people is to not use DDL with quoted names. > I'm inclined to think that we *should not ever* use quoted table or > field names unless it isn't an option (inherited database that uses > reserved words or spaces). Is this a good thought? > I really don't know if you want to support it. I for myself think names with spaces in it are a big mess. The only time when people would use quoted names is when they have to port from other databases and they have a real need to do so. But if they port, they then could do it right. There are existing tools to pump data from one db to the other. So you would have to change the metadata only. > Anyway, I still need to get back to these errors in the unit tests, but > I don't think the errors we are seeing relate directly with the > double-quoted names issue. I think that Dabo is lower()ing the field > names at some point, resulting in the name "cField" not being equal to > "cfield". I wouldn't mind telling people that dobo doesn't support spaces in names for firebird databases. But as the project leaders it is really up to you to decide on this. > >> I hope that you can look into it soon. > > I hope to as well. I've been super busy both professionally and personally. > Besides the nasty exception message """Database Execution failed with response: (-501, "Error while trying to close PreparedStatement's associated result set: \n Dynamic SQL Error\n SQL error code = -501\n Attempt to reclose a closed cursor")""" firebird seems to work for me now (at least for development). Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
