Send it!
Eric Wachsmann
FlexRadio Systems
-Original Message-
From: Paul Shaffer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 21, 2006 10:53 AM
To: [EMAIL PROTECTED]; FlexRadio@flex-radio.biz
Subject: Re: [Flexradio] A more granular DB import routine?
I already mentioned my
I already mentioned my Model-View design preferences for UI.
But I didn't mention rapid prototyping with an XML persistence layer.
This saves tons of relational-object mapping work, and it's very developer
friendly --
you can change a model's properties fairly easily without breaking the database
Tim,
Excellent question. The problem here is that the old database table
does not match the new database table. Therefore, an easy copy from one
table to another is not possible. What would be needed here would be a
way to inspect a table in the import file and recreate it in the current
datab
Tim Ellison wrote:
Eric et. al.
As a matter of practice (now that I have had a few DBs disintegrate), I
normally make a backup copy of the DB before importing it into a new
version of PowerSDR. I have recently gotten into the practice of
letting new versions make their own shiny new default DB
Eric et. al.
As a matter of practice (now that I have had a few DBs disintegrate), I
normally make a backup copy of the DB before importing it into a new
version of PowerSDR. I have recently gotten into the practice of
letting new versions make their own shiny new default DBs that have all
of the
5 matches
Mail list logo
