Until persistence is added all changes to objects in the EcoSpace will be lost when the application terminates. Prolonging the<br>life of these objects beyond the life of the application is a very simple process. By adding an ECO persistence component to<br>the EcoSpace it is possible to update a persistence storage with changes made during the application's execution, this<br>persistence storage might be a local XML file, a number of supported database servers, or a custom persistence mechanism<br>to work with persistence storages that are not supported by default.<br><br>Summary<br>Making an EcoSpace persistent is a very simple process. As a consequence switching to a new database can be achieved<br>in seconds. It is also possible with a small amount of programming to identify which type of database server to connect to at<br>runtime, allowing your application to connect to the database of your customer's choice.<br>Database structure management<br>ECO is not only capable of creating your database structure, but also updating the database structure to reflect changes<br>made to your business model. Automatic database structure management saves the developer a considerable amount of<br>time when creating applications.<br>Supported databases<br>At the time of writing the following databases are supported by ECO.<br>• BlackFish.<br>• DB2 (via Delphi BDP or DBX components).<br>• InterBase (via Delphi BDP or DBX components).<br>• FireBird 2.<br>• MySQL.<br>• Oracle.<br>• SQL Server.<br>• Sybase (via Delphi BDP or DBX components).<br>• XML file.<br>More advanced persistence techniques such as mapping to an existing database, reverse engineering an existing database,<br>and using a remote persistence server will be covered in a subsequent document.
RADStudio 2007 Hotfix: March 2008<br><br>This software hotfix is being provided to licensed users of RADStudio 2007. <br>Installation and use is governed by the license statement for RADStudio 2007.<br><br>This Hotfix applies to:<br><br>Product: RADStudio 2007, C++Builder 2007, Delphi 2007<br>Version: 2007<br>Update level: December 2007 Update<br>Editions: Professional, Enterprise, Architect<br>Languages: English, German, French, Japanese<br><br>Description of updates that are included in this hotfix:<br><br>1. AV when implicitly building C++ static library project as a dependency of another project.<br><br>Quality Central Tracking Number(s): 56584<br>Internal Tracking Number(s): 257090<br>Files affected: bcbide100.bpl and bcbide100.jdbg<br><br>2. Compiling more than 100 packages at a time can result in IDE instability and spurious build errors.<br><br>Quality Central Tracking Number(s): 51825<br>Internal Tracking Number(s): 257122<br>Files affected: dcc100.dll, dcc100.jdbg, dcc110il.dll and dcc110il.jdbg<br><br>3. Improve F1 Code Editor help for Delphi and Delphi.NET.<br><br>Quality Central Tracking Number(s): N/A<br>Internal Tracking Number(s): 166978<br>Files affected: HtmlHelp2120.bpl<br><br>4. Delphi Win32 compiler generates misaligned data structures causing AV.<br><br>Quality Central Tracking Number(s): 57300<br>Internal Tracking Number(s): 257295<br>Files affected: dcc32.exe, dcc100.dll and related .map and .jdbg files<br><br>5. AV when evaluating expression using Evaluate/Modify or setting Watch and Tooltip evaluation access violation.<br><br>Quality Central Tracking Number(s): 29214<br>Internal Tracking Number(s): 240161<br>Files affected: dbrtl.dcp<br><br>6. Code Completion for Delphi (Win32 and .NET) omits valid symbols from a ancestor classes.<br><br>Quality Central Tracking Number(s): 54027<br>Internal Tracking Number(s): 256083<br>Files affected: delphicoreide100.bpl<br><br>7. Hardware exception can occur when using dynamically linked runtime libraries and exceptions.<br><br>Quality Central Tracking Number(s): N/A<br>Internal Tracking Number(s): 257845<br>Files affected: cc3280mt.dll<br><br>8. Memory leak in the TOXDOMImplementation class of OpenXML.<br><br>Quality Central Tracking Number(s): 50763<br>Internal Tracking Number(s): 254291<br>Files affected: Xmlrtl100 package (and .dcp ); Oxmldom.pas, and the 2 dcus for it (release and debug)<br><br><br>Copyright 2008, CodeGear. All rights reserved.<br><br>
镍氢、镍镉充电控制专用IC MC33340-D资料<br>The MC33340 and MC33342 are monolithic control IC’s that are<br>specifically designed as fast charge controllers for Nickel Cadmium<br>(NiCd) and Nickel Metal Hydride (NiMH) batteries. These devices<br>feature negative slope voltage detection as the primary means for fast<br>charge termination. Accurate detection is ensured by an output that<br>momentarily interrupts the charge current for precise voltage<br>sampling. An additional secondary backup termination method can be<br>selected that consists of either a programmable time or temperature<br>limit. Protective features include battery over and undervoltage<br>detection, latched over temperature detection, and power supply input<br>undervoltage lockout with hysteresis. Fast charge holdoff time is the<br>only difference between the MC33340 and the MC33342. The<br>MC33340 has a typical holdoff time of 177 seconds and the MC33342<br>has a typical holdoff time of 708 seconds.<br>• Negative Slope Voltage Detection with 4.0 mV Sensitivity<br>• Accurate Zero Current Battery Voltage Sensing<br>• High Noise Immunity with Synchronous VFC/Logic<br>• Programmable 1 to 4 Hour Fast Charge Time Limit<br>• Programmable Over/Under Temperature Detection<br>• Battery Over and Undervoltage Fast Charge Protection<br>• Power Supply Input Undervoltage Lockout with Hysteresis<br>• Operating Voltage Range of 3.25 V to 18 V<br>• 177 seconds Fast Change Hold–off Time (MC33340)<br>• 708 seconds Fast Change Hold–off Time (MC33342)
