Not necessarily.
If you export and reimport them with the option
db.import_from_csv_file(...,id_map={}) and if the db is empty when
reimporting, everything works fine.
If you want to be able to import data in a database already populated, you
must have the UUID field. This is because web2py ca
On Monday, May 14, 2012 7:58:57 PM UTC+7, Ross Peoples wrote:
>
> Some databases allow you to temporarily turn off auto-generating IDs so
> that you can import a table keeping its original IDs intact. I wrote a
> database abstraction layer a few years back for another project that
> specifical
On 14 May 2012 15:36, Ross Peoples wrote:
> I have created issue 796:
> http://code.google.com/p/web2py/issues/detail?id=796
>
>
>
Thanks Massimo, Ross. This will be of great help.
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (P
I have created issue
796: http://code.google.com/p/web2py/issues/detail?id=796
While creating the issue, I noticed that I had made an error with the MSSQL
part. This was corrected in the issue.
Definitively. Please open a ticket about this. Thanks Ross.
On Monday, 14 May 2012 07:58:57 UTC-5, Ross Peoples wrote:
>
> Some databases allow you to temporarily turn off auto-generating IDs so
> that you can import a table keeping its original IDs intact. I wrote a
> database abstraction layer
Some databases allow you to temporarily turn off auto-generating IDs so
that you can import a table keeping its original IDs intact. I wrote a
database abstraction layer a few years back for another project that
specifically allowed you to make an identical copy of a database from a
MySQL datab
>
>
>
> As I understand it the id's get rebuilt if you export a table as csv-file
> and import it on another computer. When the whole database gets exported
> and imported the relationships stays consistent.
>
>
Yes, I've learned this the hard way. Moving the database between computers
is OK
On 12 May 2012 21:04, Sebastian E. Ovide wrote:
>
> what problems have you got moving the DB to another computer ?
>
As I understand it the id's get rebuilt if you export a table as csv-file
and import it on another computer. When the whole database gets exported
and imported the relationship
I find that using the ID works perfectly well... I'm using UUID only on
those situations where I need to pass it as vars/args (URLS for example) so
that hackers cannot guess the IDs
what problems have you got moving the DB to another computer ?
On Fri, May 11, 2012 at 2:07 PM, Johann Spies
I developed my original app to use uuid-crossreferences in stead of the
normal 'id'-field. The reason was that I wanted it to be consistent when I
move the database to another computer.
Now I am rewriting the app to make it more efficient and to make the code
cleaner - applying some new features
10 matches
Mail list logo
