Hi Francesco: Don't worry, it's OK.
2009/4/5 Francesco Montorsi <f18m_cpp217...@yahoo.it> > Hi Luis, > sorry for the delay with this reply! I've been very busy recently! > > Luis Eduardo Cañedo ha scritto: > > I have registered two libraries for database access that I would like to > > share with the community of wxWidgets programmers. > > > > Can you check if this request is likely to authorize their publication? > Sure. > > First, did you already write them or you plan to develop them after setting > up > their wxCode repo? > Yes, I have used these libraries for some time, and they are ready for download at: http://sourceforge.net/project/showfiles.php?group_id=257959&package_id=316401 https://sourceforge.net/project/showfiles.php?group_id=257966&package_id=316408 And you can read the descriptions at: http://somesourcecode.blogspot.com/ > > > Let's go with the first one: > > > name: wxPgsLib > I understand that "Pgs" is a short form for "Postgres" but I think it's a > bit > cryptic... also the "Lib" part is not strictly necessary (though it doesn't > harm) as basically 99% of wxCode components are built as libraries... > > What about a more comprehensive "wxPostgres"? Or maybe "wxPostgresLib"... 1-Because Postgres is a copyright of Postgres Global Development Group 2-Because "Pgs" is well known by Postgres developers 3-And "Lib" because i couldn't registrer just wxPgs and wxOra at sourceforge, and I had to change their names > > > > wxversion: 2.8 > > category: database > > language: cpp > > description: wxPgsLib is a wxWidgets libraries for Postgresql database > connection, SQL transactions and BLOBs support. > > It works in native way with using the Postgres libpq libraries > You probably already know about other DB-related wxWidgets-based > components: > > > http://wxcode.sourceforge.net/complist.php?compperpage=1000&viewmode=full&browseby=category§ion=database&page=1 > > In particular I see DatabaseLayer already interfaces with Postgres... of > course > if you already wrote the library it makes sense to register the component > anyway, but if you didn't write it yet, you may want to reconsider doing it > since there are already libraries for this kind of things... or am I > missing > something? Database Layer is OK, but wxOra and wxPgs are bit diferents becuase they are not based on JDBC, they are based in the databases native libraries OCCI for wxOraLib and libpq for wxPgsLib > > > > location: pgslib > > cdate: 2007-10-01 > > id: 146 > > status: beta > > docs: hand > > buildsys: projectfiles > > extdep: none > > wiki: disabled > > wxport: all > > samples: 1 > > approved: 0 > > author: Luis Eduardo Cañedo Ugalde > > version: 1.0.0 > > inCVS: 1 > Last, are you sure that you want to use CVS control? > There's nothing really wrong with CVS, but Subversion is more modern and > quicker > to use... I didn't know about it, how can I change this? > > > > maintainerid: 105 > > > > Maintainer SF username: eduardocanedo > > Maintainer name: Luis Eduardo Cañedo > > Maintainer mail address: luis.eduardo.can...@gmail.com > > > ====================================== > > About the other component: > > > name: wxOraLib > just like for the previous component I wonder if it's not better to use > "wxOracle" or something like that... > The same answer that wxPgsLib > > > wxversion: 2.8 > > category: database > > language: cpp > > description: wxOraLib is a wxWidgets libraries for Oracle database > connection, SQL transactions and BLOBs support. > > It works in native way using the Oracle OCCI libraries > Oracle seems not to be supported by existing wx wrappers of database > libraries. > So this component indeed looks very interesting. > > However I suspect that you probably wrapped Oracle and Postgres DB libs in > the > same interface, isn't it? > If this is the case, wouldn't be better to create a single component and > let the > user choose the DB type at runtime? > I'm probably missing something as I'm not very used to databases :) These can be together, but it is not practical and should be separated because they are written in different ways with different coverage and headers, so if you do only one library, we will load a large number of procedures that do not use. If we read the source, we'll see that the two libraries had the same methods, so, in compile time we can change easy one library for the other one. The main idea is that some one who knows other databases, as I know Postgres and Oracle, take this source as a base and rewrite the libraries for other databases > > > > location: oralib > > cdate: 2007-08-01 > > id: 147 > > status: beta > > docs: hand > > buildsys: projectfiles > > extdep: Oracle client > > wiki: disabled > > wxport: all > > samples: 1 > > approved: 0 > > author: Luis Eduardo Cañedo Ugalde > > version: 1.0.0 > > inCVS: 1 > same comment for previous component: Subversion is usually best :) > > > > maintainerid: 105 > > > Thanks! > Francesco > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > wxCode-users mailing list > wxCode-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wxcode-users > Thanks for your mail, I hope I have answered your questions.
------------------------------------------------------------------------------
_______________________________________________ wxCode-users mailing list wxCode-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxcode-users
