> I will ask, though, why use XML/XSL, why not use a format that lets
> you load the data to tables, then you do a huge number of tricks with
> it prior to generating the DDL, not the least of which is diff'ing
> current structure to see what needs to be changed.
>
Well, XML/XSLT is indeed not th
Csaba Nagy wrote:
[leaving the original text, as it is reply to an older posting]
On Fri, 2006-03-31 at 21:26, Jim Nasby wrote:
On Mar 29, 2006, at 3:25 AM, Csaba Nagy wrote:
Could somebody explain me, or point me to a resource where I can find
out what i
[leaving the original text, as it is reply to an older posting]
On Fri, 2006-03-31 at 21:26, Jim Nasby wrote:
> On Mar 29, 2006, at 3:25 AM, Csaba Nagy wrote:
>
> >> Could somebody explain me, or point me to a resource where I can find
> >> out what is the recommended practice when a live db need
On Mar 29, 2006, at 3:25 AM, Csaba Nagy wrote:
Could somebody explain me, or point me to a resource where I can find
out what is the recommended practice when a live db needs to be
replaced
with a new version of it that has a slightly different structure?
Our development infrastructure inc
On Mar 28, 2006, at 8:40 PM, Robert Treat wrote:
Depends on how much data you need to modify. For small tables, I
stick
with ALTER TABLE because it's a lot cleaner/easier. For larger
tables,
you might want to CREATE TABLE AS SELECT ..., or maybe copy out
and copy
back in.
This seems back
> Could somebody explain me, or point me to a resource where I can find
> out what is the recommended practice when a live db needs to be replaced
> with a new version of it that has a slightly different structure?
Our development infrastructure includes a development data base cluster,
with one
Hello,
> Could somebody explain me, or point me to a resource where I can find
> out what is the recommended practice when a live db needs to be replaced
> with a new version of it that has a slightly different structure?
>
> What do you usually do in a situation like this?
That's a big problem f
On Tuesday 28 March 2006 17:31, Jim C. Nasby wrote:
> On Wed, Mar 29, 2006 at 12:24:04AM +0200, SunWuKung wrote:
> > In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> > > On Tue, Mar 28, 2006 at 09:28:12PM +0200, SunWuKung wrote:
> > > > This is going to be an amateur question...
> > > >
> > > >
On Tue, 2006-03-28 at 16:24, SunWuKung wrote:
> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> says...
> > On Tue, Mar 28, 2006 at 09:28:12PM +0200, SunWuKung wrote:
> > > This is going to be an amateur question...
> > >
> > > Could somebody explain me, or point me to a resource where I can
On Wed, Mar 29, 2006 at 12:24:04AM +0200, SunWuKung wrote:
> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> says...
> > On Tue, Mar 28, 2006 at 09:28:12PM +0200, SunWuKung wrote:
> > > This is going to be an amateur question...
> > >
> > > Could somebody explain me, or point me to a resource
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
> On Tue, Mar 28, 2006 at 09:28:12PM +0200, SunWuKung wrote:
> > This is going to be an amateur question...
> >
> > Could somebody explain me, or point me to a resource where I can find
> > out what is the recommended practice when a live
On Tue, Mar 28, 2006 at 09:28:12PM +0200, SunWuKung wrote:
> This is going to be an amateur question...
>
> Could somebody explain me, or point me to a resource where I can find
> out what is the recommended practice when a live db needs to be replaced
> with a new version of it that has a sligh
SunWuKing.
> Could somebody explain me, or point me to a resource where I can find
> out what is the recommended practice when a live db needs to be replaced
> with a new version of it that has a slightly different structure?
Put the new database on a development machine.
Do a dump of the o
This is going to be an amateur question...
Could somebody explain me, or point me to a resource where I can find
out what is the recommended practice when a live db needs to be replaced
with a new version of it that has a slightly different structure?
My first guess would be to create the empty
14 matches
Mail list logo
