Be sure to compare the cost of the product to the value of your time spent re-creating the same functionality, maintaining it, and missing out on all features we keep adding to the SQL subsystem. As well as not finishing your project as soon, slipping deadlines etc. As well as delivering a weaker final application because you spent time re- creating features of Pro/Power. In most cases, for a professional developer, the license cost is very low compared to all of these costs.
However if you still need to find a way to cut corners, just use Pro, priced at $745. It's true, you miss out on the extremely powerful SQL templating feature, but you can write a small amount of JDBC code as a DMI for the cases where you want to call a stored procedure, and you'll still have all the standard CRUD operations, automatic server validation, queuing, exports, and other features of Pro. On Jun 17, 6:21 am, kensai yanesha <[email protected]> wrote: > Well, I went trough many tutorials and howtos on internet. The one was > amazing and it solved all my needs.DataSourcedefinition is in XML > and I can execute CRUD operations using storedc procedures on the > database side. I am talking about project SmartClient. One can > defineDataSourceusing this way: > > <DataSource > dbName="mydb" > tableName="mytbl" > ID="myDS" > dataSourceVersion="1" > generatedBy="SC_SNAPSHOT-2009-12-17/EVAL Deployment 2009-12-17" > serverType="sql" > > <fields> > <field name="wssSourceID" type="integer"></field> > <field name="watchID" type="integer"></field> > </fields> > > <operationBindings> > <operationBinding operationType="update" > allowMultiUpdate="true"> > <customSQL>call > spUpdateWSSWatchSources($values._watchID, > $wssSourceIDs)</customSQL> > </operationBinding> > </operationBindings> > </DataSource> > > This is very easy to write, but licence for one developer could be > very expensive, I think about almost 2000 dolars for the Power version > which supports the SQL templating, exactly putting into the XML > definiton of thedatasourceelement <customSQL> > > I can forget buying this for this project, maybe in the future. > > But what next? How to proceed withSmartGWTand SQL engine? Current > answer is using EoD SQL as ORM subsystem. There are some bad things > about loosing lazzy loading feature, etc., but in my case it seems to > be the best way now as you can see > at:http://lemnik.wordpress.com/2009/09/18/eod-sql-applied-%E2%80%93-part... > > Any your suggestion would be helpful. > > Kensai > > On 17 čvn, 09:32, kensai yanesha <[email protected]> wrote: > > > The database could be any SQL engine, so the dataserver type schould > > be sql not hibernate. > > > On 17 čvn, 06:18, kensai yanesha <[email protected]> wrote: > > > > Hello, > > > > I am new to GWT at all. My approach is to have an editable grid on the > > > client side and one or more tables on the database side (Oracle in my > > > case). Could someone post really working project with all files which > > > supports all 4 standard operations (select, insert, update, delete)? > > > In my case I want to do all these operations using stored procedures > > > to avoid SQL injection attacks. > > > > Any external link or pure sample will help. I was not able to find any > > > complete project which is I think best to learn it as complex logic. > > > > Thank you very much. > > > > Kensai > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
