ted. I think 3.2 is the oldest supported version. Why not
> upgrade to 4?
The options for uplifting severely out of date projects are to either
step-by-step migrate through older versions, or rewrite in the target
version.
Cheers,
Michael Manfre
--
You received this message because you
p install virtualenv" soon.
>
C:\Python34\Scripts\pip.exe
I recommend adding C:\Python34\Scripts to your path right after the
C:\Python34 folder (each path should be separated by a semicolon)
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google
nt-variables
If you are using a version of Python earlier than 3.4, follow the
instructions found at https://pip.pypa.io/en/latest/installing.html
Regards,
Michael Manfre
On Thursday, June 4, 2015 at 1:33:47 PM UTC-4, Steve Burrus wrote:
>
> *I am sorry Dhavi but your command didmn't work! Now
django-pyodbc-azure might be a better choice and it seems to be more
actively maintained.
On Thursday, May 21, 2015 at 8:30:33 AM UTC-4, felix wrote:
>
> El 20/05/15 14:39, Meet Bhagdev escribió:
>
> When I last checked the Django ORM did not have official support for SQL
> Server and Azure
that if you have no other choice. You will eventually get hit by a
change in a subsequent release of Django that forces you to remain on a no
longer supported version of Django while you update the hack for the new
version of Django or (better) rewrite it to use supported APIs.
Regards,
Michael Manfre
If you don't end up using Celery, another option for a periodic action is
to create a management command and schedule it to run with Task Scheduler
(http://msdn.microsoft.com/en-us/library/windows/desktop/aa383614%28v=vs.85%29.aspx).
Regards,
Michael Manfre
On Sunday, January 18, 2015 at 11:12
for a few months and I'm hoping this change will
make it easier for me to be more efficient with managing the pull requests
that have kindly been submitted.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubs
It's hard to give constructive feedback without knowing any of the specific
errors you encountered, but django-mssql only works on Windows. Depending
on the error you encountered with pymssql, you could try django-pymssql
(https://github.com/aaugustin/django-pymssql).
Regards,
Michael Manfre
diting, and the ability to change the configuration without a
deployment or service restart.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from
Report it. Migrations is a new feature and it is better to report any
encountered issues now before it is released.
Regards,
Michael Manfre
On Wednesday, July 9, 2014 3:10:26 AM UTC-4, graeme wrote:
>
> Having read through the comments on this bug:
>
> https://code.djangoprojec
>From looking at the configuration that was posted, the solution was likely
to remove "django.db.backends." from the ENGINE. That prefix is only for
backends that are included with Django.
Regards,
Michael Manfre
On Sunday, June 15, 2014 5:33:45 PM UTC-4, Ezequiel Bertti wr
/django-on-windows-talk/
[2] http://httpd.apache.org/docs/current/ssl/ssl_howto.html
Regards,
Michael Manfre
On Sunday, February 9, 2014 9:43:16 AM UTC-5, Robert Jonathan Šimon wrote:
>
> I was trying to find something on the web, but i didnt found anything. I
> want to use HTTPS with
Which database backend are you using to connect to SQL Server?
Regards,
Michael Manfre
On Friday, December 6, 2013 6:45:30 AM UTC-5, Derrick Jackson wrote:
>
> Hello all,
>
> I have a strange occurrence I'd like to share to see if any of you have
> run into the same thing. I
/fields/#django.db.models.FileField.upload_to
Regards,
Michael Manfre
On Saturday, November 23, 2013 10:33:59 AM UTC-5, Matt Lind wrote:
>
> So I am trying to modify django-jfu ( a multi uploader) to send files to a
> unique directory for every unique upload session performed. This is ju
://django-mssql.readthedocs.org/en/latest/usage.html#rawstoredproceduremanager
[2] https://code.google.com/p/pyodbc/
Regards,
Michael Manfre
On Wednesday, August 7, 2013 1:42:48 PM UTC-4, larry@gmail.com wrote:
>
> I have a django app that connects to a MySQL server in the usual way.
>
ostgresql" comments from the code.
Regards,
Michael Manfre
On Tuesday, August 6, 2013 2:18:35 PM UTC-4, Lindsey Hoyem wrote:
>
> Read a full description of the 1.2 Release here : http://bit.ly/187MJYX,
> including previews, bug fixes, and product enhancements! If your
> inter
://github.com/avidal/django-pyodbc
Regards,
Michael Manfre
On Saturday, March 23, 2013 12:35:08 AM UTC-4, Liang wrote:
>
> Sadly, django doesn't support sql server officially is the only stopper
> for me to adopt django.
>
> On Friday, 15 July 2011 09:07:23 UTC+8, Russell Ke
An access database should not be used for a production site. There are
various ways/tools for migrating from access to other databases.
Search for how to export from ms access and it should turn up a lot of
different methods for migrating to mysql or postresql.
Access to MySQL example -
grouped together. Specific user logging messages are
grouped if the filter can access the request.
Code and example LOGGING configuration can be found at
https://gist.github.com/1264432
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"D
to avoid memory bloat. This set
up basically fakes the other process modules available on linux.
I also did a bit of testing with nginx on windows. It's very resource
efficient and fast, but it didn't run well as a service on windows. It
orphaned processes when restarting the service.
Regards,
Michael
You can do this without a stored procedure, but it will require two db
queries.
Create a custom field with an overridden pre_save that fetches the
last RecordNum for the org and returns the next in the sequence.
You'll want an index on org and recordnum.
class
21 matches
Mail list logo
