Tom (and everyone else, really),

I had the duplicated metadata issue last night... the number of times a column's config was duplicated within the metadata classes was variable, but it ran between 4 and 8 or 9 times... which means a table with 30 columns ended up with a minimum of 120 colums if you took the metadata object's word for it.

Here's the story:

I needed to change the schema name I was using for Oracle, so I created a new user (which creates a new schema) and edited my DSN in the CF Admin to reflect the new user. Then I went to regen my Reactor classes... and immediately got the duplication issue. After mucking around for a few hours trying to figure out what the issue was, I noticed in the RDS panel in Eclipse that the schema being referenced was the old one, not the new one... the columns were all listed as FOOOLDSCHEMA.TABLENAME instead of BARNEWSCHEMA.TABLENAME. So I did a couple things. I set the DSN in the Administrator to not maintain client connections. I shut CF down, restarted my Oracle instance, and brought CF back up.

Then I checked the RDS data view panel in Eclipse and behold I was seeing my tables referenced at BARNEWSCHEMA.TABLENAME, so I regenerated my objects and BOOM.

All was golden. Now since you were on SQL Server 2k5 when this happened to you I'm assuming that your situation may be a bit different... but I did look in the application folders under metadata and saw that in my db-specific metadata classes was a reference to the schema... do you see this for SQL Server?

Laterz,
J



------------------------------------------------
Jared C. Rypka-Hauer
Senior Software Engineer
Alagad - http://www.alagad.com/

Member: Adobe Community Experts - ColdFusion
Certified Advanced ColdFusion Developer




-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[EMAIL PROTECTED]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Reply via email to