DataMgr 2.2 Beta 2

Posted At : October 22, 2008 6:30 AM | Posted By : Steve
Related Categories: DataMgr

Coming nearly four months after the previous beta, DataMgr 2.2 Beta 2 is finally ready. I regret having taken so long to get this build completed, but I am happy with the results.

(What is DataMgr?)

[More]

Comments (5) |

Print |

del.icio.us |

Digg It! |

Linking Blogs | 5678 Views

Related Blog Entries

DataMgr 2.2 is Gold! (January 26, 2009)
DataMgr 2.2 Release Candidate (with Documentation!) (January 7, 2009)
DataMgr 2.2 Beta 3 (with Railo support!) (December 3, 2008)
DataMgr 2.2 Beta 1 (July 25, 2008)
DataMgr 2.2 Alpha 3 (with Oracle support!) (May 28, 2008)
DataMgr 2.2 Has Math Now (February 20, 2008)
DataMgr 2.2 Alpha (with Derby support!) (January 16, 2008)

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)

[Add Comment]

OK, that was close. :) But if the check fields are there... say you have an admin field in the database as default. Well if that record was updated you wouldn't want to have the activeSchema change things back. So, great on the not adding a new record BUT... my thought was if the checkFields were in existance it would be 'non-destructive' vs updating. Of course that is just my preference.

So, as it sits now. If we had a user of "admin" and a password of "changeme"... and it checked the field user and found "admin" already existed it would change the password back to "changeme". My thought was if the key values are in place then have it ignore the update. We could perhaps have something else but that was my target. Sorry for not expressing that better before now.

# Posted By John Farrar | 10/22/08 1:12 PM

John,

Sorry about that. Not knowing how you wanted it to work, I made it work to address a need I had at the time.

What if I added an "onexists" attribute to the database element? It could have a value of "ignore" (what you want) or "update" (to meet my current need).

# Posted By Steve Bryant | 10/22/08 1:24 PM

That is awsome. I was going to ask but my brain is so deep in creating something today couldn't shift gears enough to come up with that. Sweet, simple and nice. I would suggest that default would be ignore... but can deal with it and be happy on many levels no matter what the default is.

# Posted By John Farrar | 10/22/08 1:26 PM

Good work Steve. Really like the improved data seeding feature, very cool idea to add an onexists attribute.

# Posted By John Whish | 10/23/08 2:41 AM

John,

Thanks!

John,

That change is ready now on the BER and the default is "ignore". Barring the unexpected, that will be part of the next beta.

# Posted By Steve Bryant | 10/23/08 9:29 AM

[Add Comment]

Sun	Mon	Tue	Wed	Thu	Fri	Sat
			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29	30	31