Re: [sqlite] table aliases in update

Igor Tandetnik wrote: > Baruch Burstein wrote: >> Does sqlite not support table aliases in update statements? > > Indeed it does not. > >> Is there a way >> to work around this to get the affect of >> >> update table1 t1 >>set col1 = col1 * 2 >>where col1 <=

Re: [sqlite] table aliases in update

On 1 Apr 2012, at 2:24pm, Igor Tandetnik wrote: > Simon Slavin wrote: >> On 1 Apr 2012, at 2:09pm, Baruch Burstein wrote: >> >>> update table1 t1 >>> set col1 = col1 * 2 >>> where col1 <= (select avg(col1) >>>

Re: [sqlite] table aliases in update

On Apr 1, 2012, at 3:21 PM, Simon Slavin wrote: > Can this be done with a JOIN instead of a sub-SELECT ? Not in SQLite, as the join clause is not supported in an update statement. For such functionality, look at MySQL or Postgress which do support variation of such syntax. Something like

Re: [sqlite] table aliases in update

Simon Slavin wrote: > On 1 Apr 2012, at 2:09pm, Baruch Burstein wrote: > >> Does sqlite not support table aliases in update statements? Is there a way >> to work around this to get the affect of >> >> update table1 t1 >> >>set col1 = col1 * 2 >>

Re: [sqlite] table aliases in update

On 1 Apr 2012, at 2:09pm, Baruch Burstein wrote: > Does sqlite not support table aliases in update statements? Is there a way > to work around this to get the affect of > > update table1 t1 > >set col1 = col1 * 2 > >where col1 <= (select avg(col1) > >

Re: [sqlite] table aliases in update

Baruch Burstein wrote: > Does sqlite not support table aliases in update statements? Indeed it does not. > Is there a way > to work around this to get the affect of > > update table1 t1 >set col1 = col1 * 2 >where col1 <= (select avg(col1) >

Re: [sqlite] table aliases in update

On Apr 1, 2012, at 3:09 PM, Baruch Burstein wrote: > Does sqlite not support table aliases in update statements? Nope, no aliasing in the update itself. > Is there a way > to work around this to get the affect of > > update table1 t1 > >set col1 = col1 * 2 > >where col1 <= (select

[sqlite] table aliases in update

Does sqlite not support table aliases in update statements? Is there a way to work around this to get the affect of update table1 t1 set col1 = col1 * 2 where col1 <= (select avg(col1) from table1 where col2=t1.col2); -- Programming today is

Re: [sqlite] Table aliases

I agree with Tom. With the proper indexes a single table for all languages is the way to go. I don't think a view for each language is necessary--just make a function that takes language and whatever you use to look up the localized strings, and returns the localized string. Further, there are

Re: [sqlite] Table aliases

Hi Shaun, > It'd be extremely useful if I were able to alias a table as > "CurrentLanguage" as opposed to directly referencing the actual > name. This saves me from having to tweak my lookup statements on > the fly to change the table name being accessed. Is it possible to > perform

Re: [sqlite] Table aliases

Hi, yes, creating a table will duplicate your data. However, a view will not: create view CurrentLanguage as select * from SomeLanguage; see http://www.sqlite.org/lang_createview.html Martin Shaun Seckman (Firaxis) wrote: > Happy Friday everyone! > > I've got several tables

[sqlite] Table aliases

Happy Friday everyone! I've got several tables each representing a specific language which my application uses to access translated strings. It'd be extremely useful if I were able to alias a table as "CurrentLanguage" as opposed to directly referencing the actual name. This