If you had to give one reason why Fox rocks, what would it be?
The UI and reporting tools are good, but there are other products out
there that do those things as well or better. The language is OO and
can be quite elegant, but it is also procedural and can be quite
ugly. And DBFs are not exactly the ultimate data store around.
No, if I had to name the killer feature, it would be this: an
internal data engine. With this, you can do things that other
languages simply cannot. You can pull a data set from SQL Server or
Postgres, and then manipulate that data quickly and powerfully, using
Fox's SQL engine as well as its Xbase commands. You can select a
subset from that cursor, and then join that subset to another cursor.
All in Fox, and all natively.
This was the piece that Dabo lacked, and that I felt would take
it from a second-rate data framework to a first-class product. Well,
I'm thrilled to announce that Dabo now has such an internal data
engine! Data in Dabo is held in objects called DataSets, but which
are very much like Fox cursors. These DataSet objects now understand
SQL, allowing you to send it any valid SQL statement and get back the
results in another DataSet object.
http://dabodev.com/wiki/DataSet
-- Ed Leafe
That is great news. I'll take a look at it this coming weekend. Thanks Ed
for all the hard work.
Craig Boyd, CEO
SweetPotato Software, Inc.
Website: www.sweetpotatosoftware.com
Tel: 507-562-0020 Fax: 507-562-0456
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On
Behalf Of Ed Leafe
Sent: Monday, November 07, 2005 12:34 PM
To: profoxtech@leafe.com
Subject: [NF] Dabo reaches another milestone
If you had to give one reason why Fox rocks, what would it be?
The UI and reporting tools are good, but there are other products out there
that do those things as well or better. The language is OO and can be quite
elegant, but it is also procedural and can be quite ugly. And DBFs are not
exactly the ultimate data store around.
No, if I had to name the killer feature, it would be this: an internal
data engine. With this, you can do things that other languages simply
cannot. You can pull a data set from SQL Server or Postgres, and then
manipulate that data quickly and powerfully, using Fox's SQL engine as well
as its Xbase commands. You can select a subset from that cursor, and then
join that subset to another cursor.
All in Fox, and all natively.
This was the piece that Dabo lacked, and that I felt would take it from
a second-rate data framework to a first-class product. Well, I'm thrilled to
announce that Dabo now has such an internal data engine! Data in Dabo is
held in objects called DataSets, but which are very much like Fox cursors.
These DataSet objects now understand SQL, allowing you to send it any valid
SQL statement and get back the results in another DataSet object.
http://dabodev.com/wiki/DataSet
-- Ed Leafe
[excessive quoting removed by server]
On 11/7/05, Ed Leafe <ed@leafe.com> wrote:
> I'm thrilled to announce that Dabo now has such an internal data
> engine! Data in Dabo is held in objects called DataSets, but which
> are very much like Fox cursors. These DataSet objects now understand
> SQL, allowing you to send it any valid SQL statement and get back the
> results in another DataSet object.
Awesome! Time to reload dabo on my machines and give it a run-thorugh.
Congratulations, Ed, on this terrific milestone!
--
Ted Roche
Ted Roche & Associates, LLC
Kudos to you all!
Chet
PS: URL is not responding -- too many hits, eh?
Ed Leafe wrote:
> If you had to give one reason why Fox rocks, what would it be?
> The UI and reporting tools are good, but there are other products out
> there that do those things as well or better. The language is OO and
> can be quite elegant, but it is also procedural and can be quite
> ugly. And DBFs are not exactly the ultimate data store around.
>
> No, if I had to name the killer feature, it would be this: an
> internal data engine. With this, you can do things that other
> languages simply cannot. You can pull a data set from SQL Server or
> Postgres, and then manipulate that data quickly and powerfully, using
> Fox's SQL engine as well as its Xbase commands. You can select a
> subset from that cursor, and then join that subset to another cursor.
> All in Fox, and all natively.
>
> This was the piece that Dabo lacked, and that I felt would take
> it from a second-rate data framework to a first-class product. Well,
> I'm thrilled to announce that Dabo now has such an internal data
> engine! Data in Dabo is held in objects called DataSets, but which
> are very much like Fox cursors. These DataSet objects now understand
> SQL, allowing you to send it any valid SQL statement and get back the
> results in another DataSet object.
>
> http://dabodev.com/wiki/DataSet
>
> -- Ed Leafe
> -- http://leafe.com
> -- http://dabodev.com
>
>
>
>
>
[excessive quoting removed by server]
Ed, you must feel terrific, having pulled this off. I have got to find a
way to carve out some time to start working with it! I loaned out my "Day
Stretcher" to "someone", and need to get it back.
Seriously, congratulations!
Gil
Gilbert M. Hale
New Freedom Data Resources
Pittsford, NY
585-359-8085
gil@gilhale.com
> -----Original Message-----
> From: profoxtech-bounces@leafe.com
> [mailto:profoxtech-bounces@leafe.com]On Behalf Of Ed Leafe
> Sent: Monday, November 07, 2005 1:34 PM
> To: profoxtech@leafe.com
> Subject: [NF] Dabo reaches another milestone
>
>
> If you had to give one reason why Fox rocks, what would it be?
> The UI and reporting tools are good, but there are other products out
> there that do those things as well or better. The language is OO and
> can be quite elegant, but it is also procedural and can be quite
> ugly. And DBFs are not exactly the ultimate data store around.
>
> No, if I had to name the killer feature, it would be this: an
> internal data engine. With this, you can do things that other
> languages simply cannot. You can pull a data set from SQL Server or
> Postgres, and then manipulate that data quickly and powerfully, using
> Fox's SQL engine as well as its Xbase commands. You can select a
> subset from that cursor, and then join that subset to another cursor.
> All in Fox, and all natively.
>
> This was the piece that Dabo lacked, and that I felt would take
> it from a second-rate data framework to a first-class product. Well,
> I'm thrilled to announce that Dabo now has such an internal data
> engine! Data in Dabo is held in objects called DataSets, but which
> are very much like Fox cursors. These DataSet objects now understand
> SQL, allowing you to send it any valid SQL statement and get back the
> results in another DataSet object.
>
> http://dabodev.com/wiki/DataSet
>
> -- Ed Leafe
> -- http://leafe.com
> -- http://dabodev.com
>
>
>
>
>
[excessive quoting removed by server]
Ed,
Congratulations! Dabo has moved to the top of my list to evaluate as
soon as I get caught up with my current batch of projects.
Malcolm
Yup, that is the Mother of all Features.
Congratulations on this achievement! Very impressive.
Bill
> If you had to give one reason why Fox rocks, what would it be?
> The UI and reporting tools are good, but there are other
> products out
> there that do those things as well or better. The language is OO and
> can be quite elegant, but it is also procedural and can be quite
> ugly. And DBFs are not exactly the ultimate data store around.
>
> No, if I had to name the killer feature, it would be this: an
> internal data engine. With this, you can do things that other
> languages simply cannot. You can pull a data set from SQL Server or
> Postgres, and then manipulate that data quickly and
> powerfully, using
> Fox's SQL engine as well as its Xbase commands. You can select a
> subset from that cursor, and then join that subset to another
> cursor.
> All in Fox, and all natively.
>
> This was the piece that Dabo lacked, and that I felt would take
> it from a second-rate data framework to a first-class product. Well,
> I'm thrilled to announce that Dabo now has such an internal data
> engine! Data in Dabo is held in objects called DataSets, but which
> are very much like Fox cursors. These DataSet objects now understand
> SQL, allowing you to send it any valid SQL statement and get
> back the
> results in another DataSet object.
>
http://dabodev.com/wiki/DataSet
-- Ed Leafe
[excessive quoting removed by server]
-----Opprinnelig melding-----
Fra: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] PÃÂ¥ vegne av Ed Leafe
< These DataSet objects now understand
SQL, allowing you to send it any valid SQL statement and get back the
results in another DataSet object. >
Damn, that's sweet! From the looks of it, I am very impressed. Would you mind sharing how you were able to do this in python?
Thanks,
Eyvind.
On Nov 8, 2005, at 3:13 AM, Eyvind Axelsen wrote:
> Damn, that's sweet! From the looks of it, I am very impressed.
> Would you mind sharing how you were able to do this in python?
Never! It's a proprietary secret!!
Actually, it was amazingly simple: I incorporated the open-
source library SQLite (http://www.sqlite.org/), and its Python
wrapper, pysqlite (http://initd.org/tracker/pysqlite). SQLite can
create in-memory databases that require no disk presence, meaning
that they are very fast and clean up after themselves when you drop
the connection. The only hard part I had to do was to manage the
conversion of the data from Python lists into the database, and vice-
versa with the results.
-- Ed Leafe