Thread: Re: [Dev-C++] Dev-C++ with SQL
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
dev-cpp-users
|
From: David M. <ci...@ya...> - 2003-08-16 01:41:17
|
mySQL++ seems to be the best one out there. http://www.mysql.com/downloads/api-mysql++.html ----- Original Message ----- From: "André Macário Barros" <and...@su...> To: "Dev-Cpp-Users" <dev...@li...> Sent: Friday, August 15, 2003 3:31 PM Subject: [Dev-C++] Dev-C++ with SQL > Dear Users, > > 1) Is it possible develop SQL code inside a C code in the Dev-C++ > environment? > 2) Is it possible develop SQL code inside a C++ code in the Dev-C++ > environment? > 3) If "Yes" for 1) and/or 2) do you know where can I get a free > documentation > for free download? > > Regards > Andre Barros > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
|
From: Reid T. <Rei...@at...> - 2003-08-18 11:46:55
|
postgresql is an excellent choice also. reid > -----Original Message----- > From: David McKen [mailto:ci...@ya...]=20 > Sent: Friday, August 15, 2003 9:33 PM > To: Andr=E9" "Mac=E1rio" Barros; Dev-Cpp-Users > Subject: Re: [Dev-C++] Dev-C++ with SQL >=20 >=20 > mySQL++ seems to be the best one out there. > http://www.mysql.com/downloads/api-mysql++.html >=20 > ----- Original Message -----=20 > From: "Andr=E9 Mac=E1rio Barros" <and...@su...> > To: "Dev-Cpp-Users" <dev...@li...> > Sent: Friday, August 15, 2003 3:31 PM > Subject: [Dev-C++] Dev-C++ with SQL >=20 >=20 > > Dear Users, > > > > 1) Is it possible develop SQL code inside a C code in > the Dev-C++ > > environment? > > 2) Is it possible develop SQL code inside a C++ code > in the Dev-C++ > > environment? > > 3) If "Yes" for 1) and/or 2) do you know where can I > get a free > > documentation > > for free download? > > > > Regards > > Andre Barros > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by: Free pre-built ASP.NET > sites including > > Data Reports, E-commerce, Portals, and Forums are > available now. > > Download today and enter to win an XBOX or Visual Studio > .NET. > > > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet _072303_01/01 > _______________________________________________ > Dev-cpp-users mailing list Dev...@li... > TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/= 01 _______________________________________________ Dev-cpp-users mailing list Dev...@li... TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm https://lists.sourceforge.net/lists/listinfo/dev-cpp-users |
|
From: Ed C. <em...@ed...> - 2003-08-18 12:54:05
|
> postgresql is an excellent choice also. Yes, but MySQL is faster, smaller, more stable, and just as free... > -----Original Message----- > From: David McKen [mailto:ci...@ya...] > Sent: Friday, August 15, 2003 9:33 PM > To: Andr=E9" "Mac=E1rio" Barros; Dev-Cpp-Users > Subject: Re: [Dev-C++] Dev-C++ with SQL >=20 >=20 > mySQL++ seems to be the best one out there. > http://www.mysql.com/downloads/api-mysql++.html >=20 > ----- Original Message ----- > From: "Andr=E9 Mac=E1rio Barros" <and...@su...> > To: "Dev-Cpp-Users" <dev...@li...> > Sent: Friday, August 15, 2003 3:31 PM > Subject: [Dev-C++] Dev-C++ with SQL >=20 >=20 > > Dear Users, > > > > 1) Is it possible develop SQL code inside a C code in > the Dev-C++ > > environment? > > 2) Is it possible develop SQL code inside a C++ code > in the Dev-C++ > > environment? > > 3) If "Yes" for 1) and/or 2) do you know where can I > get a free > > documentation > > for free download? > > > > Regards > > Andre Barros > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by: Free pre-built ASP.NET > sites including > > Data Reports, E-commerce, Portals, and Forums are > available now. > > Download today and enter to win an XBOX or Visual Studio > .NET. > > > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet _072303_01/01 > _______________________________________________ > Dev-cpp-users mailing list Dev...@li... > TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including = Data Reports, E-commerce, Portals, and Forums are available now. Download = today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/= 01 _______________________________________________ Dev-cpp-users mailing list Dev...@li... TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm https://lists.sourceforge.net/lists/listinfo/dev-cpp-users ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including = Data Reports, E-commerce, Portals, and Forums are available now. Download = today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/= 01 _______________________________________________ Dev-cpp-users mailing list Dev...@li... TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm https://lists.sourceforge.net/lists/listinfo/dev-cpp-users |
|
From: Reid T. <Rei...@at...> - 2003-08-18 17:12:07
|
It all depends on what you are planning to use it for. Note that I ended my statement with the word "also", I was just offeringa an alternative, with alternative options/capabilities. A quick search on google will provide hours of reference/opinions to refute/support/decide for yourself which is better for your purposes( eg the table below listing features that are not supported my MySql( Sub-selects No Transactions Yes, however InnoDB table type must be used Foreign key support No Views No Stored procedures No Triggers No Unions No Full joins No Constraints No.) Are any of these requirements for your development/use??? etc. So speed and size come with their own expenses. For most uses I do not think that the speed differences would be noticeable to the user or developer. I am not aware of any postgresql stability issues either. And I do not know the sizes of either MySQL or PostgreSQL as size has not been a limiting factor. http://www.webtechniques.com/archives/2001/09/jepson/ MySQL's claim to fame is that it provides a reasonable set of features, such as built-in SQL functions, that follow the 80/20 rule: It has the 20 percent of SQL capabilities that are needed for 80 percent of database applications. Developers of simple applications can live without the remaining features, such as stored procedures and subqueries, or can work around them with creative client-side programming. PostgreSQL, on the other hand, provides more features than MySQL. These include more SQL functions, server-side procedural languages, and sophisticated methods for date manipulation. PostgreSQL also offers object-relational capabilities and geometric data types. If you're developing an application that has highly complex business rules, PostgreSQL lets you handle business logic on the database server. ...... Article continues. http://www.mysql.com/doc/en/MySQL-PostgreSQL_features.html notes comparison with v7.2 of postgresql, which is now at v7.3.4. http://asia.cnet.com/builder/architect/db/0,39009328,39062643,00.htm COMMENTARY-- I'm often asked, "Do you prefer PostgreSQL or MySQL?" My answer is always the same: "It's a matter of preference." Here is a comparison of MySQL and PostgreSQL databases, offered not for the sake of voicing my opinion, but to help you make your own decision. Both systems have much to offer in terms of stability, flexibility, and performance. MySQL has features that PostgreSQL lacks, and vice versa. However, my primary focus is to help you determine which of the two databases to use in your own development. Before getting into the side-by-side comparison, I need to make it clear I'm referring to default installations. MySQL has many different table types that support transactions and foreign keys and are compliant with ACID. However, some of the configurations of these table types are quite complex. Not many Web developers or programmers use the additional table types found in MySQL. With that said, let's compare these two products. Feature list Table A is a side-by-side comparison of some of the more frequently used features of MySQL and PostgreSQL. Table A is not an exhaustive list of features, data types, or performance issues relating to these two database systems-it just gives a view of what each has to offer. From the table we see that PostgreSQL offers overall features for traditional database applications, while MySQL focuses on faster performance for Web-based applications. Open source development will bring more features to subsequent releases of both databases. Table A POSTGRESQL MYSQL ANSI SQL compliance Closer to ANSI SQL standard Follows some of the ANSI SQL standards Performance Slower Faster Sub-selects Yes No Transactions Yes Yes, however InnoDB table type must be used Database replication Yes Yes Foreign key support Yes No Views Yes No Stored procedures Yes No Triggers Yes No Unions Yes No Full joins Yes No Constraints Yes No Windows support Yes Yes Vacuum (cleanup) Yes No ODBC Yes Yes JDBC Yes Yes Different table types No Yes MySQL and PostgreSQL comparison When to use MySQL Why would you use MySQL over PostgreSQL? First, we need to consider the needs of the applications in terms of database requirements. If I want to create a Web application and performance is an issue, MySQL will be my choice because it's fast and designed to work well with Web-based servers. However, if I want to create another application that demands transactions and foreign key references, PostgreSQL is the choice. As an open source developer, I work with both databases on a regular basis, and I typically use all the features of a given database in the design and development process. It wouldn't suffice for me to use PostgreSQL for a database-driven Web site when my application requires performance. Even though MySQL is not fully compliant with the ANSI SQL standard, I should mention that, while PostgreSQL is closer to the ANSI SQL standard, MySQL is closer to the ODBC standard. Let me suggest some reasons for using MySQL over PostgreSQL: * MySQL is relatively faster than PostgreSQL. * Database design will be simpler. * You can create a basic Web-driven Web site. * MySQL's replication has been thoroughly tested. * There's no need for cleanups in MySQL (Vacuum). When to use PostgreSQL Not many Web developers use PostgreSQL because they feel that the additional features degrade performance. For example, some of the features I use are foreign key references, triggers, and views. They allow me to hide the complexity of the database from the application, thus avoiding the creation of complicated SQL commands. I know many developers who prefer the rich functionality of PostgreSQL's SQL commands. One of the most notable differences between MySQL and PostgreSQL is the fact that you can't do nested subqueries of subselects in MySQL. PostgreSQL follows many of the SQL ANSI standards, thus allowing the creation of complex SQL commands. Let me suggest some reasons for using PostgreSQL over MySQL: * Complex database design * Moving away from Oracle, Sybase, or MSSQL * Complex rule sets (i.e., business rules) * Use of procedural languages on the server * Transactions * Use of stored procedures * Use of geographical data * R-Trees (i.e., used on indexes) http://brainscraps.com/faq/pg_my.html Are there any good reasons to choose PostgreSQL over MySQL? (updated for PostgreSQL 7.3 and MySQL 4) Rick Morris ri...@br... To start with, comparing PostgreSQL and MySQL directly is a serious mistake. The real question is "what kinds of applications do you want to build?". I have had experience building complex web-based applications with both MySQL (mainly against my will) and PostgreSQL, and here are some of the conclusions I reached: The basic (over)generalization I often hear is: use MySQL for basic dynamic websites, and very lightweight (read: non-critical) applications, but use PostgreSQL for Serious stuff. Well, this is not a bad generalization, but even for lightweight applications, PostgreSQL can really save you some time, and a lot of server-side code, if you bother to learn about views, constraints, stored procedures, triggers, etc... Here are just the basics on what MySQL lacks, which PostgreSQL covers nicely: (I know MySQL is working on some of them, but it is rather late in the game, it seems to me...)..... Article continues reid > -----Original Message----- > From: Ed Cottrell [mailto:em...@ed...]=20 > Sent: Monday, August 18, 2003 8:54 AM > To: 'Dev-Cpp-Users' > Subject: RE: [Dev-C++] Dev-C++ with SQL >=20 >=20 > > postgresql is an excellent choice also. >=20 > Yes, but MySQL is faster, smaller, more stable, and just as free... >=20 |
|
From: Ed C. <em...@ed...> - 2003-08-18 21:25:06
|
That's not entirely accurate, either... MySQL does support subqueries (sub-selects) with updates as of v. 4.1.0 (out to 82 levels deep). = Foreign keys are supported by MySQL in InnoDB tables. UNION is supported as of 4.0.0. The only join not supported in MySQL is the full outer join (left outer join and right outer join are supported). As for constraints - = it's often (usually) better to implement these things in your own code. More = time consuming, yes, but often more efficient. If you want to compare any two databases, go here: http://www.mysql.com/information/features.html. Yes, that's MySQL's = version of the way things are, but it's also pretty darned accurate, and independently verifiable. For what it's worth, some large brokerage = firms and Yahoo! Finance use MySQL as a backend. My $.02. -Ed -----Original Message----- From: Reid Thompson [mailto:Rei...@at...]=20 Sent: Monday, August 18, 2003 1:11 PM To: Ed Cottrell; Dev-Cpp-Users Subject: RE: [Dev-C++] Dev-C++ with SQL It all depends on what you are planning to use it for. Note that I = ended my statement with the word "also", I was just offeringa an alternative, = with alternative options/capabilities. A quick search on google will provide hours of reference/opinions to refute/support/decide for yourself which = is better for your purposes( eg the table below listing features that are = not supported my MySql( Sub-selects No Transactions Yes, however InnoDB table type must be used Foreign key support No Views No Stored procedures No Triggers No Unions No Full joins No Constraints No.) Are any of these requirements for your development/use??? etc. So speed = and size come with their own expenses. For most uses I do not think that = the speed differences would be noticeable to the user or developer. I am = not aware of any postgresql stability issues either. And I do not know the = sizes of either MySQL or PostgreSQL as size has not been a limiting factor. http://www.webtechniques.com/archives/2001/09/jepson/ MySQL's claim to fame is that it provides a reasonable set of features, = such as built-in SQL functions, that follow the 80/20 rule: It has the 20 = percent of SQL capabilities that are needed for 80 percent of database = applications. Developers of simple applications can live without the remaining = features, such as stored procedures and subqueries, or can work around them with creative client-side programming. PostgreSQL, on the other hand, provides more features than MySQL. These include more SQL functions, server-side procedural languages, and sophisticated methods for date manipulation. PostgreSQL also offers object-relational capabilities and geometric data types. If you're developing an application that has highly complex business rules, = PostgreSQL lets you handle business logic on the database server. ...... Article continues. http://www.mysql.com/doc/en/MySQL-PostgreSQL_features.html notes = comparison with v7.2 of postgresql, which is now at v7.3.4. http://asia.cnet.com/builder/architect/db/0,39009328,39062643,00.htm COMMENTARY-- I'm often asked, "Do you prefer PostgreSQL or MySQL?" My = answer is always the same: "It's a matter of preference." Here is a comparison = of MySQL and PostgreSQL databases, offered not for the sake of voicing my opinion, but to help you make your own decision. Both systems have much to offer in terms of stability, flexibility, and performance. MySQL has features that PostgreSQL lacks, and vice versa. However, my primary focus is to help you determine which of the two databases to use in your own development. Before getting into the side-by-side comparison, I need to make it clear = I'm referring to default installations. MySQL has many different table types that support transactions and foreign keys and are compliant with ACID. However, some of the configurations of these table types are quite = complex. Not many Web developers or programmers use the additional table types = found in MySQL. With that said, let's compare these two products. Feature list Table A is a side-by-side comparison of some of the more frequently used features of MySQL and PostgreSQL. Table A is not an exhaustive list of features, data types, or = performance issues relating to these two database systems-it just gives a view of = what each has to offer. From the table we see that PostgreSQL offers overall features for traditional database applications, while MySQL focuses on faster performance for Web-based applications. Open source development = will bring more features to subsequent releases of both databases. Table A POSTGRESQL MYSQL ANSI SQL compliance Closer to ANSI SQL standard Follows some of the ANSI SQL standards Performance Slower Faster Sub-selects Yes No Transactions Yes Yes, however InnoDB table type must be used Database replication Yes Yes Foreign key support Yes No Views Yes No Stored procedures Yes No Triggers Yes No Unions Yes No Full joins Yes No Constraints Yes No Windows support Yes Yes Vacuum (cleanup) Yes No ODBC Yes Yes JDBC Yes Yes Different table types No Yes MySQL and PostgreSQL comparison When to use MySQL Why would you use MySQL over PostgreSQL? First, we need to consider the needs of the applications in terms of database requirements. If I want = to create a Web application and performance is an issue, MySQL will be my choice because it's fast and designed to work well with Web-based = servers. However, if I want to create another application that demands = transactions and foreign key references, PostgreSQL is the choice. As an open source developer, I work with both databases on a regular = basis, and I typically use all the features of a given database in the design = and development process. It wouldn't suffice for me to use PostgreSQL for a database-driven Web site when my application requires performance. Even though MySQL is not fully compliant with the ANSI SQL standard, I should mention that, while PostgreSQL is closer to the ANSI SQL = standard, MySQL is closer to the ODBC standard. Let me suggest some reasons for using MySQL over PostgreSQL: * MySQL is relatively faster than PostgreSQL. * Database design will be simpler. * You can create a basic Web-driven Web site. * MySQL's replication has been thoroughly tested. * There's no need for cleanups in MySQL (Vacuum). When to use PostgreSQL Not many Web developers use PostgreSQL because they feel that the = additional features degrade performance. For example, some of the features I use = are foreign key references, triggers, and views. They allow me to hide the complexity of the database from the application, thus avoiding the = creation of complicated SQL commands. I know many developers who prefer the rich functionality of PostgreSQL's SQL commands. One of the most notable differences between MySQL and PostgreSQL is the fact that you can't do nested subqueries of subselects in MySQL. PostgreSQL follows many of the = SQL ANSI standards, thus allowing the creation of complex SQL commands. Let me suggest some reasons for using PostgreSQL over MySQL: * Complex database design * Moving away from Oracle, Sybase, or MSSQL * Complex rule sets (i.e., business rules) * Use of procedural languages on the server * Transactions * Use of stored procedures * Use of geographical data * R-Trees (i.e., used on indexes) http://brainscraps.com/faq/pg_my.html Are there any good reasons to = choose PostgreSQL over MySQL? (updated for PostgreSQL 7.3 and MySQL 4) Rick Morris ri...@br... To start with, comparing PostgreSQL and MySQL directly is a serious = mistake. The real question is "what kinds of applications do you want to build?". = I have had experience building complex web-based applications with both = MySQL (mainly against my will) and PostgreSQL, and here are some of the conclusions I reached: The basic (over)generalization I often hear is: use MySQL for basic = dynamic websites, and very lightweight (read: non-critical) applications, but = use PostgreSQL for Serious stuff. Well, this is not a bad generalization, = but even for lightweight applications, PostgreSQL can really save you some = time, and a lot of server-side code, if you bother to learn about views, constraints, stored procedures, triggers, etc... Here are just the basics on what MySQL lacks, which PostgreSQL covers nicely: (I know MySQL is working on some of them, but it is rather late = in the game, it seems to me...)..... Article continues reid > -----Original Message----- > From: Ed Cottrell [mailto:em...@ed...] > Sent: Monday, August 18, 2003 8:54 AM > To: 'Dev-Cpp-Users' > Subject: RE: [Dev-C++] Dev-C++ with SQL >=20 >=20 > > postgresql is an excellent choice also. >=20 > Yes, but MySQL is faster, smaller, more stable, and just as free... >=20 |
