![]() | |
#21
| |||||
| |||||
|
|
Sorry, Tony. I did mean to comment that only you mentioned them. Got lost in my mind while writing the post. It just bothered me that these were such obvious possible solutions, yet almost no one was willing to mention them. |
|
MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. |
|
So we keep them hidden away, and don't talk about them in public. But isn't Cache doing the same thing? Yet I don't see them receiving the same treatment. |
|
Maybe there's something about OnGroup that I don't know. (I must admit I don't know much about them). Is their customer base happy with them? Do they have VARs? Are they successful as a company? What kind of installs do they have? (I only know of a New York State agency install.) Has anyone on this newsgroup had any experience with them or know anything more about them? |
|
Tony Gravagno wrote: Sholom wrote: Both jBase and OnGroup are part of the "MultiValue family", and I don't see why they shouldn't be recommended to someone who's needs match their solution. I did recommend both of these options two days ago. T |
#22
| |||
| |||
|
|
MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. I recall telling somewhere there that I would like to be more excited by their product, but my angle was somewhat opposite. I want to use current software development tools and languages against a better data model than that in SQL-DBMS tools. Given that they do the opposite of my interest on both ends, it isn't on my radar at this point. I do understand that they have filled a role of helping VARs who would otherwise not get business due to the non-standard DBMS, migrate their product so that it runs on Oracle, for example. I know that is no small thing, so I can say "bravo" for any successes at least. |
|
No. My understanding is that Cache' has a data model that at least addresses three of my issues with standard SQL-DBMS's: 3VL, 1NF and lack of lists. Cache has an implementation of SQL like they have an implementation of Pick. While they built it into their toolset in a very integral way, SQL is not altogether standard as it addresses non-1NF structures. Their data model is neither Pick nor relational, but MUMPs, based originally on a toolset developed about the same time as Pick, used extensively in the medical profession, for example. |
#23
| |||
| |||
|
|
dawn wrote: MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. I recall telling somewhere there that I would like to be more excited by their product, but my angle was somewhat opposite. I want to use current software development tools and languages against a better data model than that in SQL-DBMS tools. Given that they do the opposite of my interest on both ends, it isn't on my radar at this point. I do understand that they have filled a role of helping VARs who would otherwise not get business due to the non-standard DBMS, migrate their product so that it runs on Oracle, for example. I know that is no small thing, so I can say "bravo" for any successes at least. I can appreciate your interest, but that wasn't what the poster wanted. The poster has SQL machines, and wants to move his MV application to one. He wasn't asking for a better data model than relational. We have a responsibility to provide information that is best for him/her, not what interests/is best, for us. |
|
No. My understanding is that Cache' has a data model that at least addresses three of my issues with standard SQL-DBMS's: 3VL, 1NF and lack of lists. Cache has an implementation of SQL like they have an implementation of Pick. While they built it into their toolset in a very integral way, SQL is not altogether standard as it addresses non-1NF structures. Their data model is neither Pick nor relational, but MUMPs, based originally on a toolset developed about the same time as Pick, used extensively in the medical profession, for example. Again, I can appreciate your position. It's a good reason why you don't have an interest in OnGroup. But I still find the deafening silence from everyone disturbing. Whether we like the relational model or not, it is the DB of the vast majority of the universe, and it is a valid solution for someone who has some reason for wanting to go to it. |
#24
| |||
| |||
|
|
On Feb 19, 4:53 pm, sh <sham... (AT) prupipe (DOT) com> wrote: dawn wrote: MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. I recall telling somewhere there that I would like to be more excited by their product, but my angle was somewhat opposite. I want to use current software development tools and languages against a better data model than that in SQL-DBMS tools. Given that they do the opposite of my interest on both ends, it isn't on my radar at this point. I do understand that they have filled a role of helping VARs who would otherwise not get business due to the non-standard DBMS, migrate their product so that it runs on Oracle, for example. I know that is no small thing, so I can say "bravo" for any successes at least. I can appreciate your interest, but that wasn't what the poster wanted. The poster has SQL machines, and wants to move his MV application to one. He wasn't asking for a better data model than relational. We have a responsibility to provide information that is best for him/her, not what interests/is best, for us. You are right -- I got this thread confused with the one where I gave a list of possible products for a new app. Sorry 'bout that. No. My understanding is that Cache' has a data model that at least addresses three of my issues with standard SQL-DBMS's: 3VL, 1NF and lack of lists. Cache has an implementation of SQL like they have an implementation of Pick. While they built it into their toolset in a very integral way, SQL is not altogether standard as it addresses non-1NF structures. Their data model is neither Pick nor relational, but MUMPs, based originally on a toolset developed about the same time as Pick, used extensively in the medical profession, for example. Again, I can appreciate your position. It's a good reason why you don't have an interest in OnGroup. But I still find the deafening silence from everyone disturbing. Whether we like the relational model or not, it is the DB of the vast majority of the universe, and it is a valid solution for someone who has some reason for wanting to go to it. Yes, agreed. Again, for some reason I confused this with the other thread. If there is a target DBMS that a site wishes to migrate to for every app and they do not care about how the app is written, just that it uses that particular DBMS, then if either jBASE or OnGroup permits that DBMS as a backend, it might be worth considering such a migration. Thanks. --dawn- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - |
#25
| |||
| |||
|
|
On Feb 19, 11:02 pm, "dawn" <dawnwolth... (AT) gmail (DOT) com> wrote: On Feb 19, 4:53 pm, sh <sham... (AT) prupipe (DOT) com> wrote: dawn wrote: MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. I recall telling somewhere there that I would like to be more excited by their product, but my angle was somewhat opposite. I want to use current software development tools and languages against a better data model than that in SQL-DBMS tools. Given that they do the opposite of my interest on both ends, it isn't on my radar at this point. I do understand that they have filled a role of helping VARs who would otherwise not get business due to the non-standard DBMS, migrate their product so that it runs on Oracle, for example. I know that is no small thing, so I can say "bravo" for any successes at least. I can appreciate your interest, but that wasn't what the poster wanted. The poster has SQL machines, and wants to move his MV application to one. He wasn't asking for a better data model than relational. We have a responsibility to provide information that is best for him/her, not what interests/is best, for us. You are right -- I got this thread confused with the one where I gave a list of possible products for a new app. Sorry 'bout that. No. My understanding is that Cache' has a data model that at least addresses three of my issues with standard SQL-DBMS's: 3VL, 1NF and lack of lists. Cache has an implementation of SQL like they have an implementation of Pick. While they built it into their toolset in a very integral way, SQL is not altogether standard as it addresses non-1NF structures. Their data model is neither Pick nor relational, but MUMPs, based originally on a toolset developed about the same time as Pick, used extensively in the medical profession, for example. Again, I can appreciate your position. It's a good reason why you don't have an interest in OnGroup. But I still find the deafening silence from everyone disturbing. Whether we like the relational model or not, it is the DB of the vast majority of the universe, and it is a valid solution for someone who has some reason for wanting to go to it. Yes, agreed. Again, for some reason I confused this with the other thread. If there is a target DBMS that a site wishes to migrate to for every app and they do not care about how the app is written, just that it uses that particular DBMS, then if either jBASE or OnGroup permits that DBMS as a backend, it might be worth considering such a migration. Thanks. --dawn- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - I don't have the docs to hand atm, but I'm pretty sure I read that you could persist your data on DB2 using the same old UniVerse application software. Wasn't that on the CD they were handing out when Susie was on her world tour? Mike. |
#26
| |||
| |||
|
|
You are right -- I got this thread confused with the one where I gave a list of possible products for a new app. Sorry 'bout that. |
|
No. My understanding is that Cache' has a data model that at least addresses three of my issues with standard SQL-DBMS's: 3VL, 1NF and lack of lists. Cache has an implementation of SQL like they have an implementation of Pick. While they built it into their toolset in a very integral way, SQL is not altogether standard as it addresses non-1NF structures. Their data model is neither Pick nor relational, but MUMPs, based originally on a toolset developed about the same time as Pick, used extensively in the medical profession, for example. |
#27
| |||
| |||
|
|
On Feb 20, 6:29 am, "Mike Preece" <mich... (AT) preece (DOT) net> wrote: On Feb 19, 11:02 pm, "dawn" <dawnwolth... (AT) gmail (DOT) com> wrote: On Feb 19, 4:53 pm, sh <sham... (AT) prupipe (DOT) com> wrote: dawn wrote: MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. I recall telling somewhere there that I would like to be more excited by their product, but my angle was somewhat opposite. I want to use current software development tools and languages against a better data model than that in SQL-DBMS tools. Given that they do the opposite of my interest on both ends, it isn't on my radar at this point. I do understand that they have filled a role of helping VARs who would otherwise not get business due to the non-standard DBMS, migrate their product so that it runs on Oracle, for example. I know that is no small thing, so I can say "bravo" for any successes at least. I can appreciate your interest, but that wasn't what the poster wanted. The poster has SQL machines, and wants to move his MV application to one. He wasn't asking for a better data model than relational. We have a responsibility to provide information that is best for him/her, not what interests/is best, for us. You are right -- I got this thread confused with the one where I gave a list of possible products for a new app. Sorry 'bout that. No. My understanding is that Cache' has a data model that at least addresses three of my issues with standard SQL-DBMS's: 3VL, 1NF and lack of lists. Cache has an implementation of SQL like they have an implementation of Pick. While they built it into their toolset in a very integral way, SQL is not altogether standard as it addresses non-1NF structures. Their data model is neither Pick nor relational, but MUMPs, based originally on a toolset developed about the same time as Pick, used extensively in the medical profession, for example. Again, I can appreciate your position. It's a good reason why you don't have an interest in OnGroup. But I still find the deafening silence from everyone disturbing. Whether we like the relational model or not, it is the DB of the vast majority of the universe, and it is a valid solution for someone who has some reason for wanting to go to it. Yes, agreed. Again, for some reason I confused this with the other thread. If there is a target DBMS that a site wishes to migrate to for every app and they do not care about how the app is written, just that it uses that particular DBMS, then if either jBASE or OnGroup permits that DBMS as a backend, it might be worth considering such a migration. Thanks. --dawn- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - I don't have the docs to hand atm, but I'm pretty sure I read that you could persist your data on DB2 using the same old UniVerse application software. Wasn't that on the CD they were handing out when Susie was on her world tour? Mike. I know they were working on it, but am unaware of anyone actually doing that. u2-users would likely have an answer to that (http://www.u2ug.org ). --dawn |
#28
| |||
| |||
|
|
dawn wrote: MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. I recall telling somewhere there that I would like to be more excited by their product, but my angle was somewhat opposite. I want to use current software development tools and languages against a better data model than that in SQL-DBMS tools. Given that they do the opposite of my interest on both ends, it isn't on my radar at this point. I do understand that they have filled a role of helping VARs who would otherwise not get business due to the non-standard DBMS, migrate their product so that it runs on Oracle, for example. I know that is no small thing, so I can say "bravo" for any successes at least. I can appreciate your interest, but that wasn't what the poster wanted. The poster has SQL machines, and wants to move his MV application to one. He wasn't asking for a better data model than relational. We have a responsibility to provide information that is best for him/her, not what interests/is best, for us. Another point to bear in mind - he'll need a hefty load of new |
#29
| |||
| |||
|
|
MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. So we keep them hidden away, and don't talk about them in public. |
|
But isn't Cache doing the same thing? Yet I don't see them receiving the same treatment. |
#30
| |||
| |||
|
|
(Somehow this posting wasn't published, retrying) Thanks Sholom. sh wrote: MV people seem (to me) to treat OnGroup like heretics because they use Oracle or SQLServer as the backend DB, rather than a pure MV model. So we keep them hidden away, and don't talk about them in public. From what I've seen, ONware is good software that has a very specific niche. I'd like to work with it but I've never been asked. I think the part of their problem with industry perceptions is that the message from ONgroup doesn't speak to the typical MV developer. They're in a weird position because MV guys generally don't want Oracle or SQL Server. I think, could be wrong, the only companies they're going to sell to are VARs or end-users who are highly motivated to run over one of these relational databases. There are two types of companies who fit this category: You have the MV VAR who has decided to get the best of both worlds by selling a relational solution to people who want such a thing, but using familiar MV development tools. This requires some major conscious decisions which most MV people are reluctant to make. The net result for their company could be a big benefit, but for those who say "we sell applications and not databases" the initiative may achieve nothing at all. The results depend on the approach. You have the MV end-user site who is compelled to make changes, either because they feel their net worth will be higher because they use a mainstream database, or because they have someone at high levels insisting that relational is the only way to go. This site can get tremendous bang for buck by using ONware rather than doing a full port to relational, spending millions of dollars, etc. The database can be ported in the near term, the rules in the longer term in a controlled process. In fact, there's no real business or technical need to migrate the rules in this case. The only problem with this is that traditional MV code doesn't allow for referential integrity checks by the DBMS, so either that relational feature needs to be forfeited, or the MV code needs to be modified to accommodate it. I know nothing about how they handle such things. |
![]() |
| Thread Tools | |
| Display Modes | |
| |