> > But thinking more about hijacking "RowID" I am glad this is now a separate > thread. Lack of a reseverd "RowID" column name to guarantee unambiguous > record operations by general SQLite tools is a potential thread to data > security IMO. > > I would very much appreciate if this could be addressed in a future version > of SQLite! > have you seen here http://www.sqlite.org/autoinc.html ? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
- [sqlite] Ticket 3128: DISTINCT -> GROUP BY can lead to... Bradley A. Town
- Re: [sqlite] Ticket 3128: DISTINCT -> GROUP BY ca... Ralf Junker
- Re: [sqlite] Ticket 3128: DISTINCT -> GROUP B... Ralf Junker
- Re: [sqlite] Ticket 3128: DISTINCT -> GRO... Bradley Town
- Re: [sqlite] Ticket 3128: DISTINCT ->... Ralf Junker
- [sqlite] SQLite allows "RowID&... Bradley A. Town
- Re: [sqlite] SQLite allows &quo... Ralf Junker
- Re: [sqlite] SQLite allows ... Federico Granata
- Re: [sqlite] SQLite allows ... Ralf Junker
- Re: [sqlite] SQLite allows ... Darren Duncan
- Re: [sqlite] SQLite allows ... Ralf Junker
- Re: [sqlite] SQLite allows ... Darren Duncan
- Re: [sqlite] SQLite allows ... Ralf Junker
- Re: [sqlite] SQLite allows ... Darren Duncan
- Re: [sqlite] SQLite allows ... D. Richard Hipp
- Re: [sqlite] SQLite allows ... Federico Granata
- Re: [sqlite] SQLite allows ... Darren Duncan
- Re: [sqlite] SQLite allows ... Federico Granata