On Sun, May 15, 2011 at 10:00 PM, Roger Binns <rog...@rogerbinns.com> wrote:
> On 05/15/2011 07:48 PM, romtek wrote: > > I was describing what I have to do during design time, which often > happens > > after a website has been launched and is operational. > > Huh? You launch and have a site in production and then you design it? > I don't know about how things work in your world, but in mine requirements for apps change sometimes, so I have to enter design stage after an app (may be a website) has been released. Perhaps, you are a clairvoyant genius who can foresee everything that would ever be required by your clients and also produce defect-free software, but I have to work with my limitations, so I modify my software as new requirements or bugs emerge :) > You as a developer have a schema, triggers, indices, queries, templates and > other code that all work together. You also need need to have a plan for > how changes are made (and rolled back) in production. > > SQLite does not come with a magic function that does this. No one else has > written anything that precisely meets your needs because every situation > and > code base is sufficiently different. > I've simply requested from SQLite devs to add an internal mechanism to facilitate renaming columns, not a magic function. Simon has understood exactly what's needed. Let's not make this issue into something that it's not. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
