This is a discussion on RE: Whatcha' wanta have????? within the Informix forums, part of the Database Server Software category; --> Web services: >> It is becoming standard. DB2 and Oracle already have it. Also BEA Tuxedo >> middleware. MSSQL ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Web services: >> It is becoming standard. DB2 and Oracle already have it. Also BEA Tuxedo >> middleware. MSSQL and Sybase announced. Don't let Informix be an isolated >> data island! > >It is becoming standard? Which standard? Definitely not ANSI SQL standard. I see that all big RDBMS have it (or soon will have). It does not mean that because others have then Informix have to have it too. But it means that at Informix should evaluate such a possibility. And my personal view is that Informix should implement Web services somehow. I see that it is useful : many database applications are currently using web services. So in case of evaluating "which database will be best for our new application" this feature would be quite important. >> DB2 also have interesting extension: you can use web service similar as >> stored procedure. >> In Informix it extends stored procedure implementation method. Currently >> Informix have: >> - SPL; >> - J/SQL (Internet Foundation only); >> - C databalades. >> I want to add to this list: >> - Web Services. >Implement them as a DataBlade? I do not know internals of IDS implementation. It seems that DataBlade would be good for this. >> ad 2. >> For BYTE, TEXT, CLOB, and BLOB types there are no literals. Why? It just >> complicates simple things. >> For TEXT and CLOB it would be the same literal as for char(30000) column. >> For BYTE and BLOB it have to be some hex literal. > >This *is* a huge PITA. Not quite. I do not want to introduce 2GB literals. Current limitation - 255 characters is ok. Suppose you have char_col1 as char(30000). Then I can update it in following way: "set char_col1=NULL", "set char_col1='' ", "set char_col1='N/A' ", "set char_col1='NONE'", "set char_col1[1,2]='TX'" Above is typical: large column often uses short literals. With TEXT type I can't do this. So people implements their own workarounds. Typical approach is: instead of using TEXT we have several varchar columns and value is splitted between them. This is useful with not extra large BLOBS only. I just want to have such possibilities for TEXT and CLOB too. And Informix already have some kind of BLOB literals. In ODBC TEXT value is treated similarly as long varchar, which means that in ODBC BLOB literal can be used. Unfortunately I had problems with my ODBC and I couldn't verify the documentation. So this is strange: ODBC connection have BLOB literals, native connection does not. Better is to have support on server side so stored procedures would use literals too. Literals for BYTE and BLOB: I don't have urgent need for this. Just for completness it would be usefull to write in update: "set byte_col1=#FFAA" Robert Sosnowski =========================== Wiadomość ta oraz wszelkie załączone do niej pliki są poufne i mogą być prawnie chronione. Jeżeli nie jest Pan/Pani zamierzonym adresatem niniejszej wiadomości, nie może Pan/Pani jej ujawniać, kopiować, dystrybuować ani też w żaden inny sposób udostępniać lub wykorzystywać. O błędnym zaadresowaniu wiadomości prosimy niezwłocznie poinformować nadawcę i usunąć wiadomość. =========================== This email and any attached files are confidential and may be legally privileged. If you are not the intended recipient, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this email. sending to informix-list |
| ||||
| Sosnowski Robert wrote: > > Web services: >>> It is becoming standard. DB2 and Oracle already have it. Also BEA Tuxedo >>> middleware. MSSQL and Sybase announced. Don't let Informix be an >>> isolated data island! >> >>It is becoming standard? Which standard? > Definitely not ANSI SQL standard. I see that all big RDBMS have it (or > soon will have). > It does not mean that because others have then Informix have to have it > too. But it means that at Informix should evaluate such a possibility. > And my personal view is that Informix should implement Web services > somehow. I see that it is useful : many database applications are > currently using web services. > So in case of evaluating "which database will be best for our new > application" this feature would be quite important. Yes, I can remember when the promise of run-anywhere Java was going to redefine the whole application development business. Everyone made a JVM available to developers so that they could port their code anywhere. Hands up the number of people who use it, please? I can see web services being the next Java: loads of hype, it will find a niche and the rest of the world will move on looking for the Next Big Thing (tm). As a totally irrelevant aside, I can't believe that Java performance still sucks as bad as it does and that there are so many version-related issues. It seems that every sodding Java application I get needs a different JRE. And Java is on its way out. We lost our passion for application development in C because of this crap? >>> DB2 also have interesting extension: you can use web service similar as >>> stored procedure. >>> In Informix it extends stored procedure implementation method. Currently >>> Informix have: >>> - SPL; >>> - J/SQL (Internet Foundation only); >>> - C databalades. >>> I want to add to this list: >>> - Web Services. >>Implement them as a DataBlade? > I do not know internals of IDS implementation. It seems that DataBlade > would be good for this. Well, write one then? >>> ad 2. >>> For BYTE, TEXT, CLOB, and BLOB types there are no literals. Why? It just >>> complicates simple things. >>> For TEXT and CLOB it would be the same literal as for char(30000) >>> column. For BYTE and BLOB it have to be some hex literal. >> >>This *is* a huge PITA. > Not quite. Oh yes it is. It's probably one of the most FAQs out there. I think it's aggravating, too. > I do not want to introduce 2GB literals. Current limitation - 255 > characters is ok. Why not? -- "C'est pas parce qu'on n'a rien ŕ dire qu'il faut fermer sa gueule" - Coluche |