tag:blogger.com,1999:blog-6222893893652665733.post3102823871579100924..comments2024-01-08T00:30:35.594-08:00Comments on Cary Jensen "Let's Get Technical": An Advantage for Delphi DevelopersUnknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6222893893652665733.post-78327219186846623852015-07-06T21:20:08.232-07:002015-07-06T21:20:08.232-07:00>By comparison, nearly all set-based databases,...>By comparison, nearly all set-based databases, such as MS SQL Server and ORACLE, are not designed to provide navigational access. As a result, searching for <br />>a record in a result set means refining an underlying WHERE clause in a SQL query to reduce the resulting result set to a manageable size. The idea of opening a <br />>result set with millions of records and permitting a user to freely browse it is unthinkable.<br /><br />How is it unthinkable? Virtually all RDBMSes today offer cursors which do exactly what you just described.<br /><br />From Wikipedia:<br /><br />"In computer science, a database cursor is a control structure that enables traversal over the records in a database. Cursors facilitate subsequent processing in conjunction with the traversal, such as retrieval, addition and removal of database records. The database cursor characteristic of traversal makes cursors akin to the programming language concept of iterator.<br /><br />"Cursors are used by database programmers to process individual rows returned by database system queries. Cursors enable manipulation of whole result sets at once. In this scenario, a cursor enables the rows in a result set to be processed sequentially.<br /><br />"In SQL procedures, a cursor makes it possible to define a result set (a set of data rows) and perform complex logic on a row by row basis. By using the same mechanics, an SQL procedure can also define a result set and return it directly to the caller of the SQL procedure or to a client application."<br /><br />"A cursor can be viewed as a pointer to one row in a set of rows. The cursor can only reference one row at a time, but can move to other rows of the result set as needed."alcaldehttps://www.blogger.com/profile/14404682533930977783noreply@blogger.comtag:blogger.com,1999:blog-6222893893652665733.post-37046019076942009982009-09-07T11:22:56.788-07:002009-09-07T11:22:56.788-07:00Cool article -- while the company I work for uses ...Cool article -- while the company I work for uses Advantage. I have chosen to use a no-cost alternative that is akin to Oracle. I've gone with PostgreSQL and the DevArt pgAccess ($75) controls. It's great, super fast, easy to deploy, no licensing costs.Unknownhttps://www.blogger.com/profile/09606367195032695509noreply@blogger.comtag:blogger.com,1999:blog-6222893893652665733.post-34145905335986310812009-05-19T04:35:00.000-07:002009-05-19T04:35:00.000-07:00It was also AppBuilder, Wasabi and a few others ;-...It was also AppBuilder, Wasabi and a few others ;-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6222893893652665733.post-59949939734720725352009-05-07T01:26:00.000-07:002009-05-07T01:26:00.000-07:00thanks, interesting article, keep 'em coming !thanks, interesting article, keep 'em coming !avarhttps://www.blogger.com/profile/14818968124504943376noreply@blogger.comtag:blogger.com,1999:blog-6222893893652665733.post-42513731013242824152009-05-04T13:12:00.000-07:002009-05-04T13:12:00.000-07:00Frankly, I never understood developers trying to b...Frankly, I never understood developers trying to bring in each his own database server. As a customer, I expect applications to exploit the database server(s) I already own (and for which I have the proper resources and expertise) and where data already are. Very vertical applications may need their own specific and optimized database engine, but in most situations companies end up to manage several different engines just because of developers - in most cases what db to use shouldn't be a developer choice - but a customer one.LDShttps://www.blogger.com/profile/04633789460476801953noreply@blogger.com